You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org> on 2007/05/14 16:10:16 UTC
[jira] Resolved: (RAMPART-34) SignedEncryptedSupportingTokens
assertion does not work
[ https://issues.apache.org/jira/browse/RAMPART-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruchith Udayanga Fernando resolved RAMPART-34.
----------------------------------------------
Resolution: Invalid
Please see : https://issues.apache.org/jira/browse/RAMPART-35#action_12495607
> SignedEncryptedSupportingTokens assertion does not work
> --------------------------------------------------------
>
> Key: RAMPART-34
> URL: https://issues.apache.org/jira/browse/RAMPART-34
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core, rampart-policy
> Affects Versions: 1.2
> Environment: Axis2 1.2 , Rampart-Head , Windows XP, Apache Tomcat 5.5.23
> Reporter: Angel Todorov
> Priority: Critical
> Fix For: 1.2
>
>
> When trying to encrypt the username/password of the UsernameToken assertion, by using the SignedEncryptedSupportingTokens assertion , I get no result - username and password are sent in plaintext.
> This problem can be very easily reproduced by changing the "SignedSupportingTokens" assertion in rampart's sample01, to "SignedEncryptedSupportingTokens". This is really, core, critical functionality. Thank you very much.
> Regards,
> Angel
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.