ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Giger (JIRA)" <>
Subject [jira] [Commented] (WSS-443) Treat tokens received over TLS as "encrypted"
Date Tue, 21 May 2013 10:57:16 GMT


Marc Giger commented on WSS-443:

> The WSDL policy is "EndorsingEncryptedSupportingTokens"

via TLS? 

WSP spec says: 
"8.3 EndorsingSupportingTokens Assertion
Endorsing tokens sign the message signature, that is they sign the entire ds:Signature element
produced from the message signature"

So in my eyes a Message-Token transported over a TLS channel can never be a *Endorsed*Token.

Therefore the SAML token identified as SignedEndorsingSupportingTokens is double wrong and
should be identified as SignedEncryptedSupportingTokens...

> Treat tokens received over TLS as "encrypted"
> ---------------------------------------------
>                 Key: WSS-443
>                 URL:
>             Project: WSS4J
>          Issue Type: Bug
>            Reporter: Colm O hEigeartaigh
>            Assignee: Marc Giger
>             Fix For: 2.0
> The streaming WS-Security code treats a UsernameToken received over TLS as a SignedSupportingToken.
However, it doesn't treat it in the same way for encryption.
> In other words, a UsernameToken received over TLS should satisfy a SignedEncryptedSupportingToken
> Clarification: This seems to work when the policy is that of EncryptedSupportingToken,
but not that of a SignedEncryptedSupportingToken.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message