Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Update (and make current) the set of use cases developed by the Social Identities WG.
  2. Identify and document properties of social accounts that could be of interest to an application accepting authN events from the prominent social account providers.
  3. Collect and comment on approaches that campuses are taking to do "account linking" within their Person Registry (eg campus issued account, social account(s) used by the same person). Identify the  properties a social account could possess which would affect using it in this way.
  4. Document, and identify properties and pro's and con's, of a central gateway approach versus a local gateway approach. 
  5. Define and document how a gateway would represent the properties of a social account to an application.
  6. Provide application owners with recommendations on risk profiles when using social identities. Discuss the role of trust elevation.

Out of Scope -- DRAFT 2

  1. (Note -- this WG will be looking at the use of personal social accounts; it will NOT be looking at situations where an enterprise is using a social provider as their IDP, for access to enterprise apps outside of google)
  2. Technical requirements for Interop/deployment profile for OpenID Connect (OIDC)
  3. Recommendations on approaches for elevating a social account authN event to LoA 2.
  4. Identify pro's and con's of having students continue to use their social account to access campus business systems during their student days. Identify an interim step toward this milestone.

...