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] Groups - sstc-saml-core-2.0-cd-01b-diff.pdf uploaded


> What happened to the IssuedTo element described in
> 
> http://lists.oasis-open.org/archives/security-services/200409/
msg00051.html

I don't think minutes have been posted yet, but after about 30-45 minutes of
discussion, nobody could come to the table with clear enough semantics for
the element or its use, and Ron expressed concerns that having only an
identifier would be insufficient to express the conditions under which the
assertion was being issued (he characterized it as an authentication
statement for the issuee).

There are two defined extension points already, Conditions (for mandatory
semantics) and Advice (for optional semantics). SubjectConfirmation is
essentially a special case of the former, with the Method able to dictate
processing rules and taking the place of a condition extension's xsi:type.

If an issuer wanted to constrain use in some fashion based on the issuee,
but independent of subject confirmation, a condition would, I guess, be
created to express it.

-- Scott



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