Jump to content

Identity provider

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by AnomieBOT (talk | contribs) at 21:20, 21 November 2016 (Dating maintenance tags: {{By whom?}}). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In computing, an Identity provider (IdP), also known as Identity Assertion Provider, can:[1]

  1. provide identifiers for users looking to interact with a system
  2. assert to such a system that such an identifier presented by a user is known to the provider
  3. possibly provide other information about the user that is known to the provider

This may be achieved via an authentication module which verifies a security token that can be accepted as an alternative to repeatedly explicitly authenticating a user within a security realm.

For example: a website, application or service may allow users to log in with the credentials from a social-networking service like Facebook or Twitter; these services will act as Identity providers. The social-networking service verifies that the user is an authorized user and returns information to the website - e.g. username and email address (specific details might vary). This authentication system is called Social login.[2]

Perimeter authentication involves a user being authenticated only once (single sign-on). The user obtains a security token which is then validated by an Identity provider for each system that the user needs to access.[3]

Some Identity Assertion Providers support several security token types - such as SAML, SPNEGO, and X.509.

Sometimes Identity providers can work as proxies for other Identity providers, enabling the creation of trust relationships that can be employed[by whom?] to simplify the management of service providers.[4]

Service provider vs. Identity provider

"Provider" is a generic way of referring to both IdPs (Identity Providers) and SPs (Service Providers). There are overlaps when it comes to defining Identity providers vs. Service Providers. According to the OASIS organization that created SAML, an Identity provider is defined as "A kind of provider that creates, maintains, and manages identity information for principals and provides principal authentication to other service providers within a federation, such as with web browser profiles."[5][6][7]

In this respect, Salesforce defines an Identity provider as a trusted provider that allow users to make use of a single sign-on property to access other websites where a service provider is no more than a website that hosts applications[8] while Ping Identity sees the Service provider as a business-process outsourcing vendor or a SaaS provider who wants to simplify client access to its services and the Identity provider can be an enterprise that manages a large number of user accounts who may need secure Internet access to the Web-based applications or services of customers, employees or business partners.[9]

Service Provider

A service provider is "A role donned by a system entity where the system entity provides services to principals or other system entities", and a Federation is "An association comprising any number of service providers and identity providers." [10]

Identity Provider

In simple terms and as they relate to identity management, an Identity Provider can be described as a Service Provider for storing identity profiles and offering incentives to other SPs with the aim of federating user identities.[11][12] It should be noted however that Identity Providers can also provide services beyond those related to the storage of identity profiles.[13][14]

References

  1. ^ Using Cornell Shibboleth for Authentication in your Custom Application, 2014, Shawn Bower, cornell.edu. Retrieved 25 July 2016.
  2. ^ 9 Things You Should Know About Social Login & CRO, 2014, Rakish Soni, conversionxl.com. Retrieved 25 July 2016.
  3. ^ "Identity Assertion Providers".
  4. ^ Corporate Identity Providers, ondemand.com. Retrieved 25 July 2016.
  5. ^ Glossary for the OASIS Security Assertion Markup Language (SAML) V2.0, 2005, oasis-open.org. Retrieved 25 July 2016.
  6. ^ Cloud Authorization Use Cases Version 1.0, 2014, oasis-open.org. Retrieved 25 July 2016.
  7. ^ Mapping European IDABC Authentication Levels to SAML 2.0 - Gap analysis and recommendations, 2008, oasis-open.org. Retrieved 25 July 2016.
  8. ^ Identity Providers and Service Providers, salesforce.com. Retrieved 25 July 2016.
  9. ^ Service Providers and Identity Providers, pingidentity.com. Retrieved 25 July 2016.
  10. ^ Oasis, "Glossary for the OASIS Security Assertion Markup Language (SAML) V2.0"
  11. ^ IdP (Identity Provider), mit.edu. Retrieved 25 July 2016.
  12. ^ Identity Provider Deployment, 2008, UK Access Management Federation for Education and Research. Retrieved 25 July 2016.
  13. ^ Shibboleth identity provider offers improved access and identity management, 2015, jisc.ac.uk. Retrieved 25 July 2016.
  14. ^ You get what you pay for: managing customer access to content in a world of freemium, subscriptions and paywalls, 2015, 10duke.com. Retrieved 25 July 2016.

See also