Proposed Charter: External Identities Working Group

Name

External Identities Working Group

Sponsor

TBD

Group Leader (Chair)

Paul Caskey (UT System) <pcaskey@utsystem.edu>

Mission/Goals

(stated broadly) Moving towards the goal of making external identities as useful and trusted as those managed internally

The mission of the External Identities Working Group includes:

• Exploring/developing deployment models for using external identities in a variety of risk profiles
• Identifying and examining the components which are needed to make external identities useful across a broad array of services
• Exploring account linking
• Understanding differences between external identities and locally assigned identities
• Exploring approaches to raising the trust associated with external identities (references to other work on trust elevation, e.g. OASIS Trust Elevation Subcommittee)

Membership

Membership in the subcommittee is open to all interested parties. Members join the subcommittee by joining the mailing list, phone calls, and otherwise participating actively in the work of the subcommittee.

The chair of the working group is selected by group members.

Deliverables

1. Update (and make current) the set of use cases developed by the Social Identities WG.
2. Review existing profile frameworks and assess the need to create or recommend practices  and/or  propose how to use existing risk profile frameworks to help campuses evaluate the use of social identity providers with those situations.
   1. The framework should include the criteria used to evaluate the practices of a social provider 
   2. The framework needs to include the criteria needed to evaluate the risk requirements of applications
   3. The framework should accommodate the functionality provided by the Trust Elevation techniques used in the world.
3. Technical requirements for Interop/deployment profile for OpenID Connect (OIDC)
4. Creation of an external identities chart explaining different implementation models
5. Properties of an identity in a context or transaction that can be specified technically which help determine how much assurance to assign
6. Develop the requirements of the S2S GW, for "representing" the LoA of a Social authentication to a campus SP.

Expected End Date

The working group is expected to complete all deliverables and either close or recharter.

Required Resources

• wiki space 
• phone line for conference calls: usual Internet2 conference call line
• incommon.org group email list socialidentity@internet2.edu

Teleconferences

Reference Material