You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Ever A. Olano (JIRA)" <ji...@apache.org> on 2005/11/17 02:49:31 UTC
[jira] Created: (WSS-26) "Expires" element required when it should be optional
"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
Assigned to: 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-26) "Expires" element required when it should be optional
Posted by "Werner Dittmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-26?page=comments#action_12357855 ]
Werner Dittmann commented on WSS-26:
------------------------------------
Thanks for the interop testing.
currentls there is no such parameter to specify "forget timestamp" or so.
Will do this as an improvement in the current SVN version, pls allow a few days
for delivery :-)
Regards,
Werner
> "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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-26) "Expires" element required when it should be optional
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Updated: (WSS-26) "Expires" element required when it should
be optional
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-26?page=all ]
Christian Müller updated WSS-26:
--------------------------------
Attachment: patch_WSS-26.txt
Hi Davanum, hi Werner!
Fix to handle wsu:Timestamp element without wsu:Created an/or wsu:Expires element on the receiver side.
This fix not included api-changes to set a flag (e.g. in WSSConfig) to include/create a wsu:Created an/or wsu:Expires element o the sender side. If you need this, let me know... :o)
Regards,
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
> Attachments: patch_WSS-26.txt
>
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-26) "Expires" element required when it should
be optional
Posted by "Werner Dittmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-26?page=all ]
Werner Dittmann resolved WSS-26:
--------------------------------
Resolution: Fixed
> "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
> Attachments: patch_WSS-26.txt
>
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-26) "Expires" element required when it should be optional
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-26) "Expires" element required when it should be optional
Posted by "Werner Dittmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-26?page=comments#action_12357855 ]
Werner Dittmann commented on WSS-26:
------------------------------------
Thanks for the interop testing.
currentls there is no such parameter to specify "forget timestamp" or so.
Will do this as an improvement in the current SVN version, pls allow a few days
for delivery :-)
Regards,
Werner
> "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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-26) "Expires" element required when it should
be optional
Posted by "Werner Dittmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-26?page=all ]
Werner Dittmann resolved WSS-26:
--------------------------------
Resolution: Fixed
> "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
> Attachments: patch_WSS-26.txt
>
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Updated: (WSS-26) "Expires" element required when it should
be optional
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-26?page=all ]
Christian Müller updated WSS-26:
--------------------------------
Attachment: patch_WSS-26.txt
Hi Davanum, hi Werner!
Fix to handle wsu:Timestamp element without wsu:Created an/or wsu:Expires element on the receiver side.
This fix not included api-changes to set a flag (e.g. in WSSConfig) to include/create a wsu:Created an/or wsu:Expires element o the sender side. If you need this, let me know... :o)
Regards,
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
> Attachments: patch_WSS-26.txt
>
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org