You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "WellenLau (JIRA)" <ji...@apache.org> on 2008/05/16 23:43:55 UTC
[jira] Updated: (WSS-117) WSS4J does not supports KeyIdentifiers to
reference SAML tokens but this is allowed by the WSS specification.
Integration tesitng with owsm failed.
[ https://issues.apache.org/jira/browse/WSS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
WellenLau updated WSS-117:
--------------------------
Description:
According to wss-v1.1-spec-os-SAMLTokenProfile.pdf on - section 3.4 Identifying and Referencing Security Tokens :
The three forms of token references defined by the <wsse:SecurityTokenReference> element are defined as follows:
1)key identifier reference such as <wsse:KeyIdentifier>;
2)Direct or URI reference such as <wsse:Reference>;
3)An Embedded reference such as <wsse:Embedded>.
WSS4J uses <DirectReference> while OWSM using <KeyIdentifier> to refer to a saml token from within a <STR>. This means webservices using wss4j will not be able to interoperate with OWSM successfully.
was:
According to wss-v1.1-spec-os-SAMLTokenProfile.pdf on - section 3.4 Identifying and Referencing Security Tokens :
The three forms of token references defined by the <wsse:SecurityTokenReference> element are defined as follows:
1)key identifier reference such as <wsse:KeyIdentifier>;
2)Direct or URI reference such as <wsse:Reference>;
3)An Embedded reference such as <wsse:Embedded>.
WSS4J uses <DirectReference> while OWSM using <KeyIdentifier> to refer to a saml token from within a <STR>. This means webservices using wss4j will not be able to interoperate with OWSM.
Environment: Integration testing wss4j with owsm - failed. (was: Integration testing wss4j with owsm.)
Summary: WSS4J does not supports KeyIdentifiers to reference SAML tokens but this is allowed by the WSS specification. Integration tesitng with owsm failed. (was: WSS4J does not supports KeyIdentifiers to reference SAML tokens but this is allowed by the WSS specification.)
> WSS4J does not supports KeyIdentifiers to reference SAML tokens but this is allowed by the WSS specification. Integration tesitng with owsm failed.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WSS-117
> URL: https://issues.apache.org/jira/browse/WSS-117
> Project: WSS4J
> Issue Type: Bug
> Environment: Integration testing wss4j with owsm - failed.
> Reporter: WellenLau
> Assignee: Ruchith Udayanga Fernando
>
> According to wss-v1.1-spec-os-SAMLTokenProfile.pdf on - section 3.4 Identifying and Referencing Security Tokens :
> The three forms of token references defined by the <wsse:SecurityTokenReference> element are defined as follows:
> 1)key identifier reference such as <wsse:KeyIdentifier>;
> 2)Direct or URI reference such as <wsse:Reference>;
> 3)An Embedded reference such as <wsse:Embedded>.
> WSS4J uses <DirectReference> while OWSM using <KeyIdentifier> to refer to a saml token from within a <STR>. This means webservices using wss4j will not be able to interoperate with OWSM successfully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org