cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Maczuga (JIRA)" <>
Subject [jira] [Reopened] (CXF-7088) SignedEncryptedSupportingTokens in WS-Policy and SAML not encrypted being accepted
Date Fri, 14 Oct 2016 13:21:22 GMT


Grzegorz Maczuga reopened CXF-7088:

Hi Colm,

Actually we turn off Encryption completely to see that sent request contains just extra UsernameToken.

In such case such request is processed by CXF - with SAML Assertion being only signed, not
encrypted as required by WS-Policy. 

See file attached.

> SignedEncryptedSupportingTokens in WS-Policy and SAML not encrypted being accepted
> ----------------------------------------------------------------------------------
>                 Key: CXF-7088
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.0.6
>            Reporter: Grzegorz Maczuga
>            Assignee: Colm O hEigeartaigh
>         Attachments: message_anonymous.txt, policy.txt
> In WS-Policy that is used by service we have defined 
> <SignedEncryptedSupportingTokens/>
> Some people say that WS-SecurityPolicy 1.2 imply that also SAML assertion that is inside
WS-Security section of the message SOAP Header should be encrypted (not only signed).
> Message with SAML that is NOT encrypted is currently accepted by CXF even while policy
defines <SignedEncryptedSupportingTokens/>
> Question is: does SAML assertion fall into "SupportingTokens" category and should be
encrypted as well?
> What is your view on that? Is that a bug in Neethi?
> See
> Signed, encrypted supporting tokens are Signed supporting tokens (See section 8.2) that
are also encrypted when they appear in the wsse:SecurityHeader. Element Encryption SHOULD
be used for encrypting the supporting tokens.
> The syntax for the sp:SignedEncryptedSupportingTokens differs from the syntax of sp:SignedSupportingTokens
only in the name of the assertion itself. All nested policy is as per the sp:SignedSupportingTokens

This message was sent by Atlassian JIRA

View raw message