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] | [Elist Home]


Subject: [security-services] Question on conform-spec-007c


lines

168-169 state:

>>
Table 1 shows the protocols, protocol bindings, and profiles applicable to
each SAML assertion. For each SAML assertion to which an application or
implementation claims conformance, the claim must stipulate which of the
cells under Protocol, Protocol Binding, and Profile are supported.
>>

The issue in my mind is the phrase 

   "For each SAML assertion to which an application or implementation claims
conformance"

The problem is that often we do not have information on the types of SAML
assertions involved in a query. Consider the "lookup by artifact" or
assertion id query: any type of assertion may be returned. I guess the
quoted text implies that there may be all of the following conformant
implementations:

	SOAP SAML responder implementing lookup by artifact/assertion id for
AuthN assertions
     SOAP SAML responder implementing lookup by artifact/assertion id for
AuthN and attribute assertions
     ..

I guess there could be range of this type of conformance statements. On the
other hand, I don't see a real problem here other that its "richness".

- prateek


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


Powered by eList eXpress LLC