Closed glassfishrobot closed 15 years ago
Reported by recht@java.net
jdg6688@java.net said: Assign to Jiandong
jdg6688@java.net said: Fixed in trunk.
Now we support the following as TokenType for :
1. SAML 1.0 (1.1) assertion:
"http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1" and "urn:oasis:names:tc:SAML:1.0:assertion"
2. For SAML 2.0 assertion: "http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0" and "urn:oasis:names:tc:SAML:2.0:assertion"
mmatula@java.net said: Planning for 1.5
mmatula@java.net said: oops, marked for 1.5 by a mistake - removing
Was assigned to jdg6688@java.net
This issue was imported from java.net JIRA WSIT-1063
Marked as fixed on Wednesday, February 25th 2009, 12:48:48 am
com.sun.xml.ws.security.trust.impl.IssueSamlTokenContractImpl checks for valid token types, but "http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0" is not recognized as a SAML 2.0 token identifier - only "urn:oasis:names:tc:SAML:2.0:assertion" identified SAML 2.0.
The SAML 1.1 token type is an oasis url, so you'd expect the 2.0 version to be of the same structure. Also, from reading for example http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.html#_Toc162064958, you'd guess that the oasis url is the correct type. Probably both types should be supported for all versions.
Environment
Operating System: All Platform: All
Affected Versions
[current]