...
- Update (and make current) the set of use cases developed by the Social Identities Working Group. This should include use cases for both of these situations:
- Social account linked to a campus-issued identity
- Social account used by a non-community member.
- Identify and document properties of social accounts that could be of interest to an application accepting authentication events from the prominent social account providers.
- Define and document how a gateway would represent the properties of a social account to an application.
- Document, and identify properties and pro's and con's of, of a central gateway approach versus a local gateway approach.
- Provide application owners with recommendations on risk profiles when using social identities. (These profiles need not be based on the traditional 800-63 categories.) List and describe various approaches to trust elevation.
- Collect and comment on approaches that campuses are taking to do "account linking".
- Identify the properties a social account must/could possess which would affect using it in this way.
- Linking a campus account to a known social account, and linking a social account to an existing campus-issued account, where both accounts are used by the same person.
- Using a social account's credentials and authentication method to authenticate to a campus-issued account.
- Develop recommendations for ways that campus-owned attributes could be asserted following authentication with a social account (eg group memberships)
- Produce a set of longer-lived recommendations for practitioners, roughly comparable to the NMI-DIR documents (eg papers, not just wiki pages).
...