When working through TokenAuthenticator and TokenProvider samples, I found that there is a constant called "SecurityTokenTypes.Saml" which is defined as "http://schemas.microsoft.com/IdentityModel/2005/05/Tokens/Saml". Where as the oasis standard defines the SAML 1.1 token type as "http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1". Why is this discrepency
Why Microsoft Specific SAML Token Type?
Hot Topic
- How to do SQL query on xsd schema file in CR for VS2005?
- Problem Installing Visual C++
- Detaching outlook attachments
- Can't find BuildAction property for web project files
- Different namespace for DDEX compact framework provider
- How do I get Local help after installing VS 2005
- XAML and databaseaccess?
- Expander control
- Deleting/Purging Histories of a file in VSS 6.0
- Adopt model manually
Visual Studio
- Information about hosting xaml
- Source parameter for the IDE (vs.2k5 rc)
- Visual Source safe Over the internet?
- Error trying to connect VS 2003 to Source Control
- Specific Editor Question
- generated proxy via svcutil.exe
- LINQ install fails (May CTP)
- Keyword Expansion using Team Foundation Server?
- a problem with Exec function
- Passing Parameters to a report or report viewer
Why Microsoft Specific SAML Token Type?
FMaz
We are not using our own SAML Token Type. Where SOAP message security is used we are using the SAML Token Profile from the OASIS WSS TC.
We happen to recognise two URIs internally as referring to that token type, the OASIS URI and the identitymodel URI.
Gudge
jferrell1211
Thanks for the reply.
I was hoping to find out why microsoft has to use their own saml token type In other words, why can not microsoft use oasis only Is there some reason for this
Thanks.
Kinduril
We have our own URIs for all the token types we support out-of-the-box. We also support the appropriate OASIS URIs, including the one you cite above.
Gudge