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

asela pathberiya updated RAMPART-362:
-------------------------------------

    Attachment: saml-wcf-rampart.patch
                saml-wcf-wss4j.patch

Attaching possible fixes for rampart and also wss4j.

Thanks,
Asela.
                
> Inter-operable issue with verifying signature and decrypting message with 
> KeyInfo element when SAML token is used as protected token with WCF client 
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-362
>                 URL: https://issues.apache.org/jira/browse/RAMPART-362
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.6.0
>            Reporter: asela pathberiya
>             Fix For: 1.7.0
>
>         Attachments: saml-wcf-rampart.patch, saml-wcf-wss4j.patch
>
>
> Following error is generated in WCF client side  when verifying signature in 
> response message.  Fix for this issue may be in rampart and also in wss4j 
> source.  
> Unhandled Exception: System.ServiceModel.Security.MessageSecurityException: 
> Cannot resolve KeyInfo for verifying signature: KeyInfo 'SecurityKeyIdentifier
>     (
>     IsReadOnly = False,
>     Count = 1,
>     Clause[0] = LocalIdKeyIdentifierClause(LocalId = 
> '_726a85456101f8593e525eef434eec24', Owner = '')
>     )
> ', available tokens 'SecurityTokenResolver
>     (
>     TokenCount = 1, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to