incommon overview

18
www.incommon.org InCommon and Federated Identity Management 1 www.incommon.org

Upload: barry-johnson

Post on 11-Jan-2015

441 views

Category:

Technology


2 download

DESCRIPTION

Overview of Federated Identity Management and the InCommon Federation

TRANSCRIPT

Page 1: Incommon overview

www.incommon.org

InCommon and Federated Identity Management

1

www.incommon.org

Page 2: Incommon overview

www.incommon.org

2

What is Identity Management?

• A system of standards, procedures and technologies that provides electronic credentials to individuals.

• Maintains authoritative information about individuals.

• Establishes the trust needed for transactions.

• Facilitates and controls user access to online applications or resources.

Page 3: Incommon overview

www.incommon.org

3

Identity Management

Who are you? (identification)•Collect personally identifying information to prove you are who you say you are (identity proofing), such as drivers license, passport, or biometric data

•Assign attributes [(name, address, college or university, department, role (faculty, staff, student), major, email address]

How can you prove it? (authentication)•Verifying that the person seeking access to a resource is the one previously identified and approved

Page 4: Incommon overview

www.incommon.org

4

Key EntitiesThree entities involved in gaining access to a resource:

1.Subject (i.e. user) – The person identified and the subject of assertions (or claims) about his or her identity.

2.Identity Provider – Typically the university or organization that maintains the identity system, identity-proofs the subject and issues a credential. Also provides assertions or claims to the service provider about a subject’s identity.

3.Service Provider (sometimes called the relying party) – Owner/provider of the protected resource to which the subject would like to access. Consumes the assertion from the identity provider and makes an authorization decision.

Page 5: Incommon overview

www.incommon.org

5

Key Terms

Authentication – Verification (via a user ID and password) that a subject is associated with an electronic identifier. This is the responsibility of the identity provider.

Authorization – Determining whether a subject is eligible to gain access to a resource or service. The authorization decision is made by the service provider and is based on the attributes provided by the identity provider.

Attribute – A single piece of information associated with an electronic identity database record, such as name, phone number, group affiliation, email address, major.

Page 6: Incommon overview

www.incommon.org

6

1. Tedious user registration at all resources

2. Unreliable and outdated user data at resources

3. Different login process at each resource

4. Many different passwords

5. Identity provider may need to support multiple custom authentication methods and/or be asked for access to its identity database

Page 7: Incommon overview

www.incommon.org

The Problem

• Growing number of applications – on-campus and outsourced or hosted

• All of these service providers must:

– Verify the identity of users (faculty, staff, students, others)

– Know who’s eligible to access the service

– Know the student is active and hasn’t left school

• Increase in outsourced or cloud services raises concerns about the security and privacy of the identity data

7

Page 8: Incommon overview

www.incommon.org

A Solution: Federated Identity Management

Federation: An association of organizations that come together to exchange information, as appropriate, about their users and resources in order to enable collaborations and transactions.

All participants in a federation agree on the same policies and procedures related to identity management and the passing of attributes.

Instead of one-to-one relationships, the federation allows one-to many relationships.

8

Page 9: Incommon overview

www.incommon.org

Federated Identity Management

• Parties agree to leverage the identity provider’s database, rather than creating separate data stores

• Users no longer register with the service provider, using their university credentials for transactions

• Single sign-on convenience for users

• Identity provider does the authentication; service provider does the authorization

• Attributes are the key – maintain privacy and security

9

Page 10: Incommon overview

www.incommon.org

10

1. Single sign on

2. Services no longer manage user accounts & personal data stores

3. Reduced help-desk load

4. Standards-based technology

5. Home org and user controls privacy

Page 11: Incommon overview

www.incommon.org

Attributes: Anonymous ID, Staff, Student, …

Federated Access in 30 seconds

Metadata, certificates, common attributes & meaning, federation registration authority, Shibboleth

4. If attributes are acceptable to resource policy, access is granted!

3. Authorization: Privacy-preserving exchange of agreed upon attributes

2. Federation-based trust exchange to verify partners and locations

1. Authentication: single-sign-on at home institution

Home Institution – user signs in

Online Resource

Page 12: Incommon overview

www.incommon.org

InCommon Federation

InCommon is the federation for U.S. research and education, providing higher education and their commercial and non-profit partners with a common trust framework for access to online resources.

12

Page 13: Incommon overview

www.incommon.org

About InCommon

• Through InCommon, campuses leverage their identity databases to allow for the use of one set of credentials to access multiple resources.

• Online service providers no longer need to maintain user accounts.

• Identity providers manage the levels of their users' privacy and information exchange.

• InCommon uses SAML-based authentication and authorization systems (such as Shibboleth®) to enable scalable, trusted collaborations among its community of participants.

13

Page 14: Incommon overview

www.incommon.org

InCommon Federation Benefits

• Convenience – Single sign-on with higher education credentials

• Safety – Enhanced security with fewer data spills

• Privacy – Release of only the minimum information necessary to gain access to resources (via attributes)

• Scalability – Once implemented, federated access relatively simple to extend

• Authentication – Campus does the authentication, maintaining control of user information

• Authorization – Service provider makes access decisions based on attributes

14

Page 15: Incommon overview

www.incommon.org

InCommon Participants Year-by-Year

15

• 253 InCommon Participants (Sept. 2010)

• Almost 5 million end-users (faculty, staff, students)

Page 16: Incommon overview

www.incommon.org

16www.incommonfederation.org/participants

Page 17: Incommon overview

www.incommon.org

Federated ResourcesResources available via InCommon are many and diverse

Business Functions• Benefits• Asset management• Talent management• Visas & INS compliance• Mobile alerts• Travel management• Energy management• Surveys and market analysis

Learning and Research• Journals• Databases and analytical tools• Multi-media access• Homework labs• Quiz tools• Plagiarism detection• Software downloading• Alcohol awareness education• Student travel discounts• Transportation and ride-share

services.

Strong support from key higher education partners, such as: Microsoft, Apple, National Student Clearinghouse, NSF, NIH, Gov-affiliated Labs 17

Page 18: Incommon overview

www.incommon.org

InCommon and Federated Identity Management

18

www.incommon.org

[email protected]

[email protected]