...
- RP-Managed Selector (like our HTML mockup)
- Cloud Selector (like Janrain, Avoco, Shiboleth Discovery etc.) --formerly called "ISA" by this ULX WG (and its predecessors)
- Active Client Selector (e.g. a browser integrated application or an enhanced browser)
Trends in Recent discussions about Active Client Selectors:
- It is self-evident that the scope of ULX be limited to "next gen" active clients
- Some feel that "next gen" active clients to should rely on OAuth instead of using:
- Dedicated client UI to gather auth materials
- Dedicated UI to review/approve attribute/claim release
- WS-Trust to fetch (e.g. SAML) token
ISA Identity Selector Variations:
- User-aware vs. stateless --can we think of better names?configurable (or not) - can the IS be configured with the user's preferred set of IdPs. Being user-configurable implies that the user has an account on the IS
- Request-and-forward (ISA IS fetches token and POSTs to RP) vs. Selection-only -- can we think of better names?
...
- See http://kantarainitiative.org/confluence/display/ulx/ULX+Teleconference+2010-10-25
- Walkthrough of Finnish selector use case (eg SP-driven IdP grouping and priorities) http://kantarainitiative.org/confluence/display/ulx/Use+Case+Finnish+services+for+citizens|../../../../../../../../../display/ulx/Use+Case+Finnish+services+for+citizens||||\
Next Meeting
- Time: 08:00 PT | 11:00 ET | 16:00 UTC/GMT (Time Chart)
- Skype: +9900827042954214
- US Dial-In: +1-201-793-9022
- Room Code: 295-4214