[ http://issues.apache.org/jira/browse/WSS-26?page=comments#action_12361841 ]
Christian Müller commented on WSS-26: ------------------------------------- Hi Werner, hi Davanum! The oasis spec (http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf) defined both elements, wsu:Created and wsu:Expires, as optional. Pleas consider this... Christian > "Expires" element required when it should be optional > ----------------------------------------------------- > > Key: WSS-26 > URL: http://issues.apache.org/jira/browse/WSS-26 > Project: WSS4J > Type: Bug > Environment: n/a > Reporter: Ever A. Olano > Assignee: Davanum Srinivas > > Hello. While testing my WSS4J-based validation code using Parasoft's SOA > Test as my client, I found that WSS4J fails the validation when the request > includes a Timestamp with no "Expires" element under it. I looked at the > code and it does seem to assume that there's always an Expires element. In > fact, it also assumes that "Created" is present. In the spec, both fields > are optional. > Also, I believe the spec says the validating code SHOULD (not MUST) throw a > fault if the security semantics have expired. So, I think there should be a > way to tell WSS4J to just ignore the timestamp, if present. Or is there? > Thanks, > Ever -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
