You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Ever A. Olano (JIRA)" <ji...@apache.org> on 2006/12/21 20:47:23 UTC
[jira] Commented: (WSS-67) WSSecTimestamp should allow a
non-expiring timeToLive
[ http://issues.apache.org/jira/browse/WSS-67?page=comments#action_12460328 ]
Ever A. Olano commented on WSS-67:
----------------------------------
I was going to close this issue myself but I don't think I can. Please close it.
There is indeed a way to turn off the Expires element and that is by setting timeToLive to zero. So, this is a non-issue. Sorry about that.
Thanks!
> WSSecTimestamp should allow a non-expiring timeToLive
> -----------------------------------------------------
>
> Key: WSS-67
> URL: http://issues.apache.org/jira/browse/WSS-67
> Project: WSS4J
> Issue Type: Bug
> Environment: Any
> Reporter: Ever A. Olano
> Assigned To: Davanum Srinivas
> Priority: Minor
>
> Since the Expires element is optional in the WS-Security timestamp, there should (or must) be a way to tell WSSecTimestamp not to add it. For example, a negative timeToLive value.
> Thanks!
--
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