OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [security-services] Conformance document questions

Hi Rich,

Thanks for your comments, they were also discussed on the November 23
conference call. I have an action to respond with a proposal:

Table 4 only discusses responder conformance requirements, but does not 
define ny request requirements.  I suppose you could turn "must process"

on the responder into "must send" on the server, but is that the intent;

if so, it should be made explicit. Or is requestor conformance currently

unspecified by design?

On the conference call there was a consensus that "SAML Responder"
should be replaced by "SAML Authority" and an additional operational
mode called "SAML Requestor" be introduced into the conformance
document. This terminology is first introduced in Section 6 of Profiles
wherein Figure 6 uses the terms "Requesting System Entity" and "SAML
Authority". The profiles document will be updated by replacing
"Requesting System Entity" by "SAML Requestor".

I will introduce an operational mode called "SAML Requestor" (new column
in Table 4). All of the features (rows of Table 4) will be optional for
SAML requestors. The idea here is to provide terminology to support
statements of the type "Does your product implement the SAML requestor
role with feature XXX"?. 

The Identity Provider proxy references section of the core; 
should that be (since .6 doesn't exist)?

Agreed, this is an obsolete reference and I will update to

-- prateek

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]