ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (WSS-457) Incorrect validation of ProtectTokens assertion
Date Tue, 06 May 2014 09:12:01 GMT

     [ https://issues.apache.org/jira/browse/WSS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Colm O hEigeartaigh closed WSS-457.
-----------------------------------


> Incorrect validation of ProtectTokens assertion
> -----------------------------------------------
>
>                 Key: WSS-457
>                 URL: https://issues.apache.org/jira/browse/WSS-457
>             Project: WSS4J
>          Issue Type: Bug
>            Reporter: Colm O hEigeartaigh
>            Assignee: Marc Giger
>             Fix For: 2.0.0
>
>
> The streaming code doesn't validate the ProtectTokens assertion properly in the case
of a SymmetricBinding. The scenario is that the Signature should reference (sign) the EncryptedKey,
and also reference it in the signing KeyInfo. However, the streaming code complains with:
> Original Exception was org.apache.wss4j.policy.stax.PolicyViolationException: Token /{http://schemas.xmlsoap.org/soap/envelope/}Envelope/{http://schemas.xmlsoap.org/soap/envelope/}Header/{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security/{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}BinarySecurityToken
must be signed by its signature.
> However, the BinarySecurityToken in question is the certificate used to encrypt the symmetric
key, and not the signing credential.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


Mime
View raw message