This content has been marked as final. Show 2 replies
I think the timestamp-verification tag is out side of the config tag. Something like this:
<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd"> <key-store-file>META-INF/ikmapp.jks</key-store-file> <key-store-password>xxx</key-store-password> <key-store-type>jks</key-store-type> <trust-store-file>META-INF/wsse10.truststore</trust-store-file> <trust-store-password>xxx</trust-store-password> <config> <requires> <signature/> </requires> </config> <timestamp-verification createdTolerance="30" warnCreated="false" expiresTolerance="10" warnExpires="false"/> </jboss-ws-security>
The setting works as we just deployed a soap service and using this setting to avoid the "future timestamp" exception.
Not sure if the existing is still needed or not but we removed it.
It would be nice to have the XSD published... the schema location given is not valid.
Oh, great, it works now as expected!!!
Think you're right, the XSD should be published.