[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsfed] Using SAML meta data in WS-Fed
I have reviewed the proposal with some of the authors of the
SAML spec to ensure that it complies with both the spirit and the letter of [Samlv2Meta]
usage and extensibility. They have stated that the proposal is correct on
both counts. They believe that the only changes that the SS TC needs to make
to [Samlv2Meta] are textual changes in the specification which make it sound
more restrictive than the underlying schema actually is. That is, remove
the text that restricts entities and protocols to only SAML. I have been
told by two key authors that they believe these changes can be made simply as
errata, which they are willing to support. They do not believe that existing SAML implementations will need
to change. I was told that this will create a significant re-use for
sites, such as Shibboleth, that support both WS-Federation and SAML because
they will be able to publish all of the metadata for both protocols in a single
document. They project savings for human administrators, as well as the development
of common STS software used to publish or consume metadata at partner
configuration time. Finally, it appears this is being received as a positive step
towards harmonization between the TCs as well as the protocol stacks. --des From: Anthony Nadalin
[mailto:drsecure@us.ibm.com] Issue is that I believe there are changes need
to SAML if we go the route of using SAML metadata elements, if we don't go the
SAML route then its all contained within our TC. I'm not sure using SAML brings
more unity as we still have our own elements, its just allows us to use the
SAML metatdata elements as wrappers.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]