[
https://issues.apache.org/jira/browse/RAMPART-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved RAMPART-362.
-------------------------------------
Resolution: Fixed
Fixed on master in 87da6b67. The attached patches targeted a WSS4J fork; the
constant they add never existed in Apache
WSS4J, but the behaviour it selected is what WSS4J 4.x provides under
CUSTOM_KEY_IDENTIFIER. Rampart now references an
issued SAML token from ds:KeyInfo with a wsse:KeyIdentifier as the SAML Token
Profile requires, for both signatures and
encryption, instead of a wsse:Reference URI that a recipient cannot resolve
when the assertion is not in the message. SAML
2.0 assertions get the SAMLID value type. Covered by
IssuedTokenReferenceTest. Will ship in 2.0.0.
> 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
> Assignee: Robert Lazarski
> Priority: Major
> Fix For: 2.0.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 was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]