This is an old revision of this page, as edited by 213.132.62.70 (talk) at 09:51, 21 July 2009 (→Identity federation). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 09:51, 21 July 2009 by 213.132.62.70 (talk) (→Identity federation)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)In information technology, federated identity has two general meanings:
- The virtual reunion, or assembled identity, of a person's user information (or principal), stored across multiple distinct identity management systems. Data are joined together by use of the common token, usually the user name.
- A user's authentication process across multiple IT systems or even organizations.
For example, a traveler could be a flight passenger as well as a hotel guest. If the airline and the hotel use a federated identity management system, this means that they have a contracted mutual trust in each other's authentication of the user. The traveler could identify him/herself once as a customer for booking the flight and this identity can be carried over to be used for the reservation of a hotel room.
See also
- Athens access and identity management
- Central Authentication Service
- Digital identity
- Identity Metasystem
- Information Card
- LDAP
- Liberty Alliance
- Interop Vendor Alliance
- OpenID
- Shibboleth
- Windows CardSpace
- WS-Federation
- X.509
References
- Article from EWeek.com on "What is Federated Identity Management?
- Ping Identity on "Federated Identity Management: A Beginners Guide"
- Overview from Sun on "What is Federated Identity Management?
- Authentication Federation Article from AuthenticationWorld
- Ideating Identity