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] Action item"Relying Party tailors assertion in browser artifact profile"


Title: Action item "Relying Party tailors assertion in browser artifact profile"

Colleagues - Minutes of the last Focus Group meeting describe this action item ...

"Action item:  Tim, Simon, Prateek (champions): compose complete
recommendation for "Relying Party tailors assertion in browser
artifact profile"
    - Prateek:  Essentially closed
        - Text has been received by Prateek
        - will update draft and share with bindings group
    - Tim sent proposal to Phill, who made counter proposal, mainly
      due to differences in Core 16 & Core19
        - [ACTION: Tim] Tim to propose how to modify core19 (rather
          than core16)
    - Joe:  Try to have closed by next week"

I have examined Core 19 and convinced myself that the requirement is supported by the schema.  The authentication and attribute queries extend SubjectQueryAbstractType (which contains the Subject element, which (in turn) can be an assertionID, extracted from an artifact).  The authentication query can also specify the desired subject confirmation method, and the attribute query can also specify attribute designators.

So, the relying party can use these queries to obtain a tailored assertion, based on an existing artifact.

All the best.  Tim.

-----------------------------------------
Tim Moses
Tel: 613.270.3183



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


Powered by eList eXpress LLC