A Survey of User-Centric Identity Management Technologies
A Survey of User-Centric Identity Management Technologies
A Survey of User-Centric Identity Management Technologies
13
directory. It proves your identity if you follow the The evolution of identity management systems also
guidelines strictly, otherwise there is no proof. tends towards a simplification of user experience and
In fact, it is a single authority using an opaque trust reinforcing authentication. It is well known that poor
decision without any credentials (cryptographic proofs) usability compromises authentication. A new paradigm
choice or portability. should be introduced to solve these problems while
In the context of web access, the user must enroll for still being compatible at least with federated identity
every non-related service, generally with different user management.
interfaces and follows diverse policies and protocols. Therefore, a user oriented paradigm, called user-centric
Thus, the user has a non-consistent experience and identity management, has emerged[6,9]. This paradigm
deals with different identity copies. In addition, some is embraced by multiple industry products and
problems related to privacy have also emerged. Indeed, initiatives such as Microsoft Cardspace [12], Sxip [13]
our privacy can be potentially compromised by and Higgins Trust Framework [14]. This is Identity
websites. It is clear that sites have a privacy policy, but 2.0.
there is no control from the user on his identity. What
are the conditions for using these data? How can we 3.2. Identity Management 2.0
improve our privacy? And to what granularity will we
allow them to use it? In this section, we will explain the most popular
The same problem comes up when accessing identity management 2.0 platforms and protocols.
resources. The more resources, the more management
we have to have. It is an asymmetric trust; and the 3.2.1 XRI/XDI
policy decision may be opaque.
It allows access with an opaque trust decision and a XRIs (EXtensible Resource Identifier) [15] offer a
single centralized authority without a choice of human-friendly form of persistent identifier. That’s
credentials. It is a silo model [9] because it is neither why it is a convenient identifier for SSO systems. They
portable nor scalable. This is Identity 1.0. support both persistent and reassignable identifiers in
The identity management problems appeared in the the same syntax and establish a global context symbol.
1980s. The first identity management system was the Moreover, they enable identification of the same
Rec. X.500, developed by ITU [10], covering directory logical resource in multiple contexts and multiple
services like Directory Access Protocol (DAP). ISO versions of the same logical resource. XRI is about
was also associated with the development of the Addressing. XDI (XRI Data Exchange) is about Data
standard. Like a lot of ITU standards, this one was very Sharing protocols and uses basically XRI. Both XRI
heavy and complex. A “light” version appeared in the and XDI are being developed under the support of
1990s for DAP. This was LDAP which was OASIS. I-name and I-number registry services for
standardized by the IETF, widely used and adopted by privacy-protected digital addressing use XRI. It can be
Netscape. Microsoft has invented an equivalent Active used as an identifier for persons, machines and agents.
Directory, and for users, they introduced Passport. It is
also the ITU which standardized X.509 for identities 3.2.2 ID-WSF/Liberty
related to certificates. This is currently the
recommended format. It is a small file, generated by a In 2001, a business alliance was formed to serve as
certification authority. open standards organization for federated identity
If there is a loss or a usurpation of the certificate, it can management; it was named the Liberty Alliance [9]. Its
always be revoked by the certification authority. goals are to guarantee interoperability, support privacy,
This is for single users, but what about enterprises that and promote adoption of its specifications, guidelines
have automated their procedures and have a and best practices. The key objectives of the Liberty
proliferation of applications with de-provisioning but Alliance are to:
are still in a domain-centric model? What about 9 Enable users to protect their privacy and identity
resources shared between domains? 9 Enable SP’s to manage their client lists;
The Silo model is not interoperable and is deficient in 9 Provide an open federated SSO;
many aspects. That’s why a federated identity 9 Provide a network identity infrastructure that
management model is now emerging and it is very supports all current emerging network access
appreciated by enterprises. A federated identity devices.
management system consists of software components Liberty Alliance’s work in the first phase is to enable
and protocols that handle the identity of individuals in federated network identity management. Among
a decentralized manner throughout their identity life others, it offers SSO and linking accounts in the set of
cycle. [11]
14
SPs’ in the boundary of the trust circle. The work in protocols. OpenID authentication 2.0 is becoming an
this phase is referred to as Identity Federation open platform that supports both URL and XRI user
Framework (ID-FF). identifiers. A URL uses an IP or DNS resolution and is
In the second phase, the specifications offer enhanced unique and ubiquitously supported. It can be a personal
identity federation and interoperable identity-based digital address used as well as by bloggers, even
web services. This body is referred to as Identity Web though it is not yet largely used
Services Framework (ID-WSF). This framework The first layer supports users’ identification. OpenID
involves support of the new open standard such as WS- can identify a user using an URL or an XRI address.
Security developed in OASIS. The Security Assertion Light-Weight Identity (LID) is the original URL-based
Markup Language (SAML) is another OASIS identity protocol, and is now part of OpenID. LID is a
specification [17] that provides a set of rules for the set of protocols capable of representing and using
structure of identity assertions, protocols to move digital identities on the Internet in a simple manner,
assertions, bindings for protocols to typical message without relying on any central authority. LID supports
transport mechanisms, and profiles. Indeed, SAML is a digital identities for humans, human organizations and
set of XML and Simple Object Access Protocol non-humans (e.g. software agents, things, websites,
(SOAP) based services and formats for the exchange of etc.). It implements Yadis [22], a meta-data discovery
authentication and authorization information between service and is pluggable on all levels. On top of the
security systems. first layer, the Yadis layer is used for identity service
The Liberty Alliance specifications rely heavily on discovery for URLs and XRI resolution protocol. It
other standards such as SAML and WS-Security which uses the OASIS format called XRDS (Extensible
defines mechanisms implemented in SOAP headers. Resource Description Sequence). At the authentication
These mechanisms are designed to enhance SOAP layer, a user can prove his/her own URL or I-name
messaging by providing a quality of protection through using a credential. OpenID does not need a centralized
message integrity, message confidentiality, and single authority for enrollment and it is therefore a federated
message authentication. identity management. To ensure anonymity, IdP can
The WS-* (the Web Services protocol specifications) randomly generate a digital address used specially for
are a set of specifications that is currently under this SP. The user-centric method is realized in three
development by Microsoft and IBM. It is a part of steps:
larger efforts to define a security framework for web a. The users choose their digital identity
services, the result of the proposals are often referred b. The users choose their IdP
to as WS-*. It includes specifications such as WS- c. The users choose their SP
Policy, WS-Security Conversation, WS-Trust, and OpenID is already available on well-known Web
WS-Federation. This latter has functionality for platforms (e.g. Drupal, WordPress, etc) and its take-up
enabling pseudonyms and attribute-based interactions. seems promising.
Therefore, WS-Trust has the ability to ensure security
tokens as a means of brokering identity and trust across 3.2.5 Microsoft InfoCard/Cardspace
domain boundaries [18].
By providing users with a way to select identities
3.2.3 Shibboleth and more, Windows CardSpace (formerly Infocard)
plays an important role in the identity meta-system.
Shibboleth [19] is a project whose goal is to allow InfoCard implements the core of the Identity
universities to share their web resources subject to Metasystem, using open standard protocols to
control access. Thereby, it allows inter-operation negotiate, request and broker identity information
between institutions. It develops architectures, policy between trusted IdPs and SPs.
structure, practical technologies, and an open source In the terminology of Microsoft, the relying party is a
implementation. The key concept includes “federated” service provider (SP) in our model. To prove an
management identity whose meaning is almost the identity on a network, the user emits credentials which
same as the Liberty term’s [20]. are some proof of his identity. For example, in the
simplest digital identity, the user’s name is the identity,
3.2.4 OpenID while the password is said to be the authentication
credential. In the terminology of Microsoft and others,
The intent of the OpenID framework specifies they are called security tokens and contain one or more
layers that are independent and small enough to be claims. Each claim contains information about the user,
acceptable and adopted by the market [21]. The version like his/her name or home address, etc. In addition, the
1.0 has dealt with http-based URL authentication security token encloses proofs that the claims are
15
correctly emitted by the real user and belong to him. 9 the need for interoperability,
This could be done cryptographically by using 9 the need to respond to regulator, public or
different forms such as X.509 certificates and Kerberos customer pressure to implement solutions based
tickets but unfortunately, it is not practical for on trusted infrastructures that offer security and
transmitting different kinds of claim. As seen before, privacy, and
the standard SAML is the best for this purpose as it can 9 the lack of common interfaces for
be used to define security tokens. identity/networking systems.
Using context providers, directories and
3.2.6 SXIP communication technologies (e.g. Microsoft/IBM, WS-
*, LDAP, email, etc.) can be plugged into the Higgins
The Simple eXtensible Identity Protocol (SXIP) was framework. Higgins has become an Eclipse plug-in,
designed to provide an Internet-scalable and user- and is a project of the Eclipse Foundation. Higgins is
centric identity architecture that imitates real-world suitable for developers, users and enterprises. Higgins
interactions. relieves the developers from knowing all the details of
If a SP has integrated SXIP in his Website, which is multiple identity systems, thanks to one API that
easily done by using SDKs, it is a Membersite. When a supports many protocols and technologies: CardSpace,
subscriber of SXIP would like to have access to this OpenID, XRI, LDAP, etc. Applications written with
Membersite: the Higgins API can integrate the identity, profile, and
a) he types his URL address and clicks on [sxip in], relationship information into these heterogeneous
b) he types his URL identity issued by IdP (called systems. The Higgins Project is supported by IBM and
Homesite), Novell and thwart InfoCard Microsoft’s project.
c) the browser is redirected to the Homesite,
d) he enters his username and password, being 3.2.8 Summary Table
informed that the Membersite has requested data,
selects the related data and verify it and can select The ten requirements are those listed at the end of
to automatically release data for other visit to this Section 2. A White box means that the requirement is
Membersite and confirms, not covered, grey partially and black fully fulfilled.
e) the browser is redirected to the Membersite,
Table 1: Evaluation of Id 2.0 technologies
f) the user has access to the content of the site.
Requirement 1 2 3 4 5 6 7 8 9 10
SXIP 2.0 is a platform based on a fully decentralized
architecture providing an open and simple set of XRI/XDI
processes to exchange identity information. SXIP 2.0 ID/WSF
has significantly reduced the problems resulting from
moving identity data from one site to another. It is an Shibboleth
URL-based protocol that allows a seamless user’s
experience and fits the user-centric paradigm exactly. CardSpace
With this, the user has a full control over his identity OpenID
and has an active role in the exchange of his identity
data. Therefore, he can benefit from the portable SXIP
authentication to connect with many websites.
Thereby, the user has more choices and convenience Higgins
when exchanging his identity data and he indirectly
enables websites to offer enhanced services to their We can remark that Higgins fulfill the maximum of
subscribers. the requirements.
16
a mechanism was introduced allowing a mutual [13] J. Merrels, SXIP Identity. DIX: Digital Identity
identification of both the user and the site, and Exchange Protocol. Internet Draft, March 2006.
exploitable by everyone everywhere. Moreover the [14] Higgings Trust Framework project,
user is in the middle of the system. http://www.eclipse.org/higgins/, 2006.
That’s why the identity management systems have
[15] OASIS Working Draft Version 04, “An Introduction to
progressed and really evolved from silo models to
XRIs”, 2005.
federated user-centric models through centralized
models among others. These technologies deal with the [16] Liberty Alliance, Liberty ID-FF Architecture Overview.
problems of digital identity by managing and Liberty Alliance Project, 2005.
disclosing identity information in an open and standard [17] OASIS, Conformance Requirements for the OASIS
way. Security Assertion Markup Language (SAML) V.20, 2005.
All identity systems will coexist and they will all offer
[18] Teruko MIYATA and al., “A Survey on Identity
sufficient unique capabilities that will allow them to Management Protocols and Standards”, IEICE TRANS. INF
grow independently to some extent. In spite of the & SYST, 2006.
unique capabilities, there is a significant degree of
duplication of functionality between the various [19] Shibboleth project, http://shibboleth.internet2.edu/.
systems. A convergence between the systems would [20] Liberty Alliance, “Liberty Developer Tutorial”
eliminate such duplications and result in a simpler http://www.projectliberty.org/.
identity landscape. Indeed, Higgins’ and Liberty
[21] David Recordon VeriSign Inc, Drummond Reed,
Alliance’s projects offer a good convergence. “OpenID 2.0: A Platform for User-Centric Identity
Management”, 2006.
5. References
[22] Yadis, Yadis specification 1.0, http://yadis.org/ .
17