You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2013/02/07 12:55:12 UTC
[jira] [Resolved] (WSS-421) WSSecSignature does not allow access to
the internal BinarySecurityToken after it is applied to the security header
[ https://issues.apache.org/jira/browse/WSS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-421.
-------------------------------------
Resolution: Fixed
> WSSecSignature does not allow access to the internal BinarySecurityToken after it is applied to the security header
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WSS-421
> URL: https://issues.apache.org/jira/browse/WSS-421
> Project: WSS4J
> Issue Type: Bug
> Affects Versions: 1.6.9
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 2.0, 1.6.10
>
>
> WSSecSignature does not allow access to the internal BinarySecurityToken after it is applied to the security header (it is explicitly nulled).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org