Mailing-List: contact dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ws.apache.org
Date: Tue, 21 May 2013 09:13:16 +0000 (UTC)
From: "Colm O hEigeartaigh (JIRA)" <jira@apache.org>
To: dev@ws.apache.org
Message-ID: <JIRA.12647955.1368709482844.351962.1369127596977@arcas>
In-Reply-To: <JIRA.12647955.1368709482844@arcas>
References: <JIRA.12647955.1368709482844@arcas>
Subject: [jira] [Assigned] (WSS-443) Treat tokens received over TLS as
 "encrypted"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Colm O hEigeartaigh reassigned WSS-443:
---------------------------------------

    Assignee: Marc Giger
    
> Treat tokens received over TLS as "encrypted"
> ---------------------------------------------
>
>                 Key: WSS-443
>                 URL: https://issues.apache.org/jira/browse/WSS-443
>             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 requirement.
> 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: 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