Trend of Federated Identity Management for Web Services



Similar documents
Federated Identity Management Solutions

Web Based Single Sign-On and Access Control

Lecture Notes for Advanced Web Security 2015

New Single Sign-on Options for IBM Lotus Notes & Domino IBM Corporation

Agenda. How to configure

Flexible Identity Federation

Securing Web Services With SAML

SAML and OAUTH comparison

OpenID Deutsche telekom. Dr. Torsten Lodderstedt, Deutsche Telekom AG

Allidm.com. SSO Introduction. Discovering IAM Solutions. Leading the IAM facebook/allidm

HP Software as a Service. Federated SSO Guide

Copyright: WhosOnLocation Limited

Copyright Pivotal Software Inc, of 10

The increasing popularity of mobile devices is rapidly changing how and where we

IBM Tivoli Federated Identity Manager V6.2.2 Implementation. Version: Demo. Page <<1/10>>

Masdar Institute Single Sign-On: Standards-based Identity Federation. John Mikhael ICT Department

STUDY ON IMPROVING WEB SECURITY USING SAML TOKEN

Using SAML for Single Sign-On in the SOA Software Platform

An SAML Based SSO Architecture for Secure Data Exchange between User and OSS

MLSListings Single Sign On Implementation Guide. Compatible with MLSListings Applications

Microsoft Office 365 Using SAML Integration Guide

Extending DigiD to the Private Sector (DigiD-2)

HP Software as a Service

Symplified I: Windows User Identity. Matthew McNew and Lex Hubbard

Tenrox. Single Sign-On (SSO) Setup Guide. January, Tenrox. All rights reserved.

OpenID and identity management in consumer services on the Internet

Get Success in Passing Your Certification Exam at first attempt!

The Primer: Nuts and Bolts of Federated Identity Management

Enhancing Web Application Security

DocuSign Single Sign On Implementation Guide Published: March 17, 2016

Axway API Gateway. Version 7.4.1

SAML SSO Configuration

Enabling SAML for Dynamic Identity Federation Management

Interoperate in Cloud with Federation

WebLogic Server 7.0 Single Sign-On: An Overview

OpenSSO: Cross Domain Single Sign On

How to create a SP and a IDP which are visible across tenant space via Config files in IS

The Primer: Nuts and Bolts of Federated Identity Management

Federation Proxy for Cross Domain Identity Federation

Introduction to SAML

Identity Management in Liferay Overview and Best Practices. Liferay Portal 6.0 EE

IBM WebSphere Application Server

SWIFT: Advanced identity management

How To Use Saml 2.0 Single Sign On With Qualysguard

JOSSO 2.4. Ws-Federation Integration Tutorial

OpenLogin: PTA, SAML, and OAuth/OpenID

Server based signature service. Overview

EXTENDING SINGLE SIGN-ON TO AMAZON WEB SERVICES

About Me. Software Architect with ShapeBlue Specialise in. 3 rd party integrations and features in CloudStack

This Working Paper provides an introduction to the web services security standards.

DualShield SAML & SSO. Integration Guide. Copyright 2011 Deepnet Security Limited. Copyright 2011, Deepnet Security. All Rights Reserved.

ELM Manages Identities of 4 Million Government Program Users with. Identity Server

Digital Identity and Identity Management Technologies.

BYE BYE PASSWORDS. The Future of Online Identity. Hans Zandbelt Sr. Technical Architect. CTO Office - Ping Identity

TIB 2.0 Administration Functions Overview

Nationwide and Regional Health Information Networks and Federated Identity for Authentication and HIPAA Compliance

Negotiating Trust in Identity Metasystem

SAML Security Option White Paper

Title: A Client Middleware for Token-Based Unified Single Sign On to edugain

Digital Identity Management

Single Sign On Integration Guide. Document version:

Security solutions Executive brief. Understand the varieties and business value of single sign-on.

Implementing Identity Provider on Mobile Phone

CLAIMS-BASED IDENTITY FOR WINDOWS

SAP Single Sign-On 2.0 Overview Presentation

Setup Guide Access Manager 3.2 SP3

Authentication Integration

Using SAP Logon Tickets for Single Sign on to Microsoft based web applications

Building Secure Applications. James Tedrick

An Efficient Windows Cardspace identity Management Technique in Cloud Computing

Oracle Fusion Middleware Oracle API Gateway OAuth User Guide 11g Release 2 ( )

Google Apps Deployment Guide

Introduction to Directory Services

SAML-Based SSO Solution

Improving Security and Productivity through Federation and Single Sign-on

Abstract of the Core Concepts of S.A.F.E.: Standards for Federated Identity Management

SAML AS AN SSO STANDARD FOR CUSTOMER IDENTITY MANAGEMENT. How to Create a Frictionless, Secure Customer Identity Management Strategy

Implementation Guide SAP NetWeaver Identity Management Identity Provider

PingFederate. OpenID Cloud Identity Connector. User Guide. Version 1.1

This chapter describes how to use the Junos Pulse Secure Access Service in a SAML single sign-on deployment. It includes the following sections:

SAM Context-Based Authentication Using Juniper SA Integration Guide

CA Nimsoft Service Desk

Web Services Security and Federated Identity Management

Distributed Identity Management Model for Digital Ecosystems

Configuring ADFS 3.0 to Communicate with WhosOnLocation SAML

The Top 5 Federated Single Sign-On Scenarios

How To Use Salesforce Identity Features

Integrating Apex into Federated Environment using SAML 2.0. Jon Tupman Portalsoft Solutions Ltd

Identity Federation Broker for Service Cloud

Case Study: SSO for All: SSOCircle Makes Single Sign-On Available to Everyone

DEPLOYMENT GUIDE. SAML 2.0 Single Sign-on (SSO) Deployment Guide with Ping Identity

Test Plan Security Assertion Markup Language Protocol Interface BC-AUTH-SAML 1.0

IBM WebSphere Application Server

Transcription:

30 Trend of Federated Identity Management for Web Services Chulung Kim, Sangyong Han Abstract While Web service providers offer different approaches to implementing security, users of Web services demand simple access as if the services were provided from a single system as well as enhanced security levels. Moreover, as corporate mergers, acquisitions and alliances become increasingly prevalent, companies must respond actively to the changing environment by providing easy access and high levels of security to its employees and external associates at low costs. In order to do so, companies are deploying federated identity management technologies such as SML, OpenID and CardSpace. This paper takes a look at these technologies, examines the issues regarding the current status and developments from the perspectives of standardization, technology and market and provides an outlook for the future. Index Terms Web Services, security, federated identity management I. INTRODUCTION s corporate organizations become larger and more A complex, the numbers of people and web services related to organizations naturally increase. From the user perspective, as the numbers of ids and web services they access increase, there are demands for efficient id management and easy access to web services. At the same time, companies need to improve management efficiency for their web services, increase security levels and save costs by enhancing work efficiency for their employees as well as outside associates. One of the solutions widely used for these purposes has been single sign-on(sso), which involves central management of various web services within a company to increase id management efficiency for internal and external users and facilitate access to the services. In addition, as corporations become globalized and mergers, acquisitions and strategic alliances become increasingly frequent, system integration must be implemented at low costs to facilitate management and access to Web services for Manuscript received June 4, 2008. (Write the date on which you submitted your paper for review.) This research is supported in parts by (a) a grant(cr070019) from Seoul R&BD Program funded by the Seoul Development Institute of Korean government, (b) by the Ministry of Knowledge Economy, Korea, under the HNRC(Home Network Research Center) ITRC(Information Technology Research Center) support program supervised by the Institute of Information Technology Assessment. Chulung Kim is with INITEH co.,ltd, Seoul, Korea (e-mail: chulung.kim@ initech.com). Sangyong Han is with the Computer Science and Engineering Department, ChungAng University, Seoul, Korea, (e-mail: hansy@cau.ac.kr) employees, external associates and Web service customers. As an application provided by a particular solution vendor, SSO features proprietary functions and management mechanisms that call for prohibitive costs to implement integration, and in some cases make integration difficult in practice due to different characteristics of existing systems at various organizations. A technology currently being offered to resolve such problems is federated identity management (FIM). This paper aims to examine FIM technologies that are currently available, their mechanisms, standardization, technological status, market trends, and provide an outlook for FIM's future. The remainder of this paper is constructed as follows. Chapter 2 discusses current FIM technologies including SAML, OpenID and CardSpace. Chapter 3 examines standardization of the technologies as well as their technological and market trends. FIM's future outlook is presented in Chapter 4 and Chapter 5 provides the conclusion of the study. II. TECHNOLOGIES OF FIM FIM refers to a system that allows users to access multiple corporate networks with a single set of ID and password. Generally speaking, a company in an FIM system must trust its partners to guarantee their users. Each system participating in FIM creates a message stating that "this user has been authenticated and should be allowed to access the Web service," and a standardized algorithm is required to transmit the message [4]. This chapter introduces SAML, a standard proposed by OASIS(Organization for the Advancement of Structured Information Standards), OpenID from the Open Source group and CardSpace by Microsoft. A. SAML(Security Assertion Markup Language) SAML is an XML standard designed for exchanging authentication and authorization data between security domains, that is, between an identity provider (a producer of assertions) and a service provider. Starting with its initial v1.0, v2.0 was finalized in 2005. The basic concept of SAML is displayed in Figure 1.

31 Figure 1 Basic SAML Concept [5] A SAML assertion is a declaration of facts regarding a subject such as a user and contains three types including security-related authentication, attribute and authorization decision. A SAML protocol describes how SAML elements including SAML assertions are packaged in SAML requests and responses and defines the procedures SAML entities follow. A SAML binding defines mapping between SAML protocol messages and communication protocols. Figure 2 displays a use case, and specific procedures are as follows. 1) The user agent makes a request for a target resource to the SP(service provider). (SAML 2.0 only) 2) The SP responds to the user agent with an XHTML form. (SAML 2.0 only) 3) The user agent makes a request for an SSO service to the IdP(identity provider). (SAML 2.0 only) 4) The IdP responds to the user agent with an XHTML form. 5) The user agent makes a request for an assertion consumer service to the SP. 6) The SP redirects the user agent to the target resource. 7) The user agent makes another request for the target resource to the SP. [4] Figure 2 Example of SAML [4] B. OpenID OpenID is an open, distributed and free framework for user-oriented digital identity that takes advantages of existing Internet technologies (URI, HTTP, SSL, Diffie-Hellman). One of the IDs for existing URIs can be converted to an ID that can be used to log into the sites that support OpenID. The general OpenID protocol is as follows. 1) The end user initiates authentication (Initiation) by presenting a User-Supplied Identifier to the Relying Party via their User-Agent. 2) After normalizing (Normalization) the User-Supplied Identifier, the Relying Party performs discovery (Discovery) on it and establishes the OP(OpenID Provider) Endpoint URL that the end user uses for authentication. 3) (optional) The Relying Party and the OP establish an association (Establishing Associations) -- a shared secret established using Diffie-Hellman Key Exchange. 4) The Relying Party redirects the end user's User-Agent to the OP with an OpenID Authentication request (Requesting Authentication). 5) The OP establishes whether the end user is authorized to perform OpenID Authentication and wishes to do so. 6) The OP redirects the end user's User-Agent back to the Relying Party with either an assertion that authentication is approved (Positive Assertions) or a message that authentication failed (Negative Assertions). 7) The Relying Party verifies (Verifying Assertions) the information received from the OP [9] C. Cardspace CardSpace is an application included in Microsoft's Windows Vista OS as a default program. It provides users with a set of personal digital identities in the form of a visual "Information Card". The card can be easier to use than passwords and employ strong cryptography, offering more

32 security than traditional web-based password solutions. Participants of a CardSpace system include identity providers that issue digital identities, relaying parties that provide services and users who obtain IDs from identity providers and use them to access services provided by relaying parties. Figure 3 illustrates an intuitive user screen of CardSpace containing an information card. Figure 4 CardSpace Process Flow [12] Figure 3 Example of CardSpace User Screen [12] Figure 4 depicts CardSpace's processing flow, which consists of the following three stages. 1) First, the application gets the security token requirements of the relying party that the user wishes to access. This information is contained in the relying party's policy, and it includes things such as what security token formats the relying party will accept, and exactly what claims those tokens must contain. 2) Once it has the details of the security token this relying party requires, the application passes this information to CardSpace, asking it to request a token from an appropriate identity provider. 3) Once this security token has been received, CardSpace gives it to the application, which passes it on to the relying party. The relying party can then use this token to authenticate the user or for some other purpose. [12] III. TREND OF FIM This chapter examines FIM trends in terms of technology, standardization and market. A. Trend of Technology FIM technology can be categorized into company-controlled FIM, user-controlled FIM and a moderate FIM between the two types. In addition, more appropriate technologies are being used according to the layers shown in Figure 5. It is believed that SAML technology is the optimal solution for the company-controlled environment such as enterprise's internal systems(layer 0) and close business partners(layer 1), OpenID for the user-controlled environment designed to provide easy access to open Web services such as customers(layer 3) and potential customer(layer 4), and CardSpace for the moderate type of FIM. Figure 5 Identity Landscape 2008 [13]

33 Figure 6 Identity Mashup [14] Figure 8 Hype Cycle for Information Security B. Trend of Standardization OASIS accepted WS-Security proposed by WS-I, led by Microsoft and IBM, and established it as WSS. OASIS also released SAML v1 in 2002, accepted Liberty Alliance's suggestions regarding extensions and declared SAML v2 a standard in 2006. Figure 7 SAML Standardization Trend [15] C. Trends of Market Figure 8 illustrates the "hype cycle for information security" released by the global market survey organization Gartner Group. The graphic indicates that FIM has passed the peak of expectations, is actually needed in the market and there are solutions and services that use the technology. In reality, major Web service providers such as Google and Yahoo are in the process of implementing OpenID for their customers, an increasing number of services are dedicated to OpenID, and existing and new small and medium Web services are allowing their customers to use OpenID to access their sites. IV. OUTLOOK FOR FIM This chapter looks into the changing Web service and corporate environments to provide an outlook for the future of FIM. A. Response to User-Oriented Demands Currently being discussed with "participation" as the keyword, Web v2 is expected to meet an increasing demand for personalization through easy access to various services. OpenID is capable of satisfying such demand, and there will be more services that offer OpenID as the default means of access. Moreover, continued supply and expansion of Windows Vista will naturally increase use requirements and services for CardSpace, prompting a transition to the FIM-based Web service environment. B. Advent of Identity Risk Management Solution Increasing usage and interest in Web services bring about enhanced awareness about information protection. FIM is an identity-related information protection technology developed based on the considerations of key security issues such as 3A(authentication, authorization, availability) and secrecy. However, as FIM's scope of application expands and more users access the technology, the demand for identity risk management solution is expected to increase as legal and policy regulations regarding personal information protection are intensified. C. FIM with PKI for secure E-Commerce Since the goal of OpenID is to provide convenient user-oriented services, users can create and use IDs without providing any form of identification. However, since this approach is not appropriate for safe e-commerce services, OpenID is expected to be linked with PKI.

34 V. CONCLUSIONS This paper examined FIM technologies such as SAML, OpenID and CardSpace that provide convenient and safe access to various Web services. The study also surveyed the current status and trends in terms of technology, international standard and market. Finally, based on the findings, an outlook for FIM was presented regarding the response to user-oriented demands, increasing demands for identity risk management solutions and stronger links with PKI for safe e-commerce transactions. and the Ph.D. degree in 1984. From 1984 to 1995, he worked at Poughkeepsie Lab. And Watson Research Center in IBM, USA. His research interests include Web Technologies, Web Services, Semantic Web, Information Retrieval and Multimedia. ACKNOWLEDGMENT This research is supported in parts by (a) a grant(cr070019) from Seoul R&BD Program funded by the Seoul Development Institute of Korean government, (b) by the Ministry of Knowledge Economy, Korea, under the HNRC(Home Network Research Center) ITRC(Information Technology Research Center) support program supervised by the Institute of Information Technology Assessment. REFERENCES [1] "Federated identity", http://en.wikipedia.org/wiki/federated_identity. [2] "What is Federated Identity Management", http://www.eweek.com/c/a/past-news/whats-federated-identity-manag ement/, E-Week Company. [3] "Federated Identity Management and Web Service", http://news.zdnet.com/2100-1009_22-5535345.html, Zdnet Company. [4] "Security Assertion Markup Language", http://en.wikipedia.org/wiki/security_assertion_markup_language [5] "Security Assertion Markup Language (SAML) V2.0 Technical Overview", http://www.oasis-open.org/committees/download.php/22553/sstc-saml-t ech-overview-2%200-draft-13.pdf, OASIS. [6] "WS-Federation", http://en.wikipedia.org/wiki/ws-federation. [7] "Understanding WS-Federation", http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-fed/ WS-FederationSpec05282007.pdf?S_TACT=105AGX04&S_CMP=LP, IBM. [8] "WS-Federation 1.1 Specification", http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-fed/ WS-Federation-V1-1B.pdf?S_TACT=105AGX04&S_CMP=LP, IBM [9] What is OpenID, http://www.openid.net, OpenID Org. [10] "OpenID", http://en.wikipedia.org/wiki/openid [11] "CardSpace", http://en.wikipedia.org/wiki/windows_cardspace [12] "Windows CardSpace", http://msdn.microsoft.com/ko-kr/netframework/aa663320(en-us).aspx, Microsoft [13] "The Identity Landscape of 2008", http://netmesh.info/jernst The Perfect Stome Identity Mashup, [14] http://www.andredurand.com/2006/09/20.html#a534, Andredurand Company [15] Liberty Technology Tutorials, http://www.projectliberty.org, Liberty Alliance [16] Hype Curve for Information Security, http://www.gartner.com, Gartner Group [17] "Identity 2.0 tops 2008 trends in identity management", http://www.sourcewire.com/releases/rel_display.php?relid=37436&hilit e= Chulung Kim is a Security R&D Team Leader at INITECH co, Ltd in Korea. He received Master degree of Computer Science and Engineering in College of Engineering from ChungAng University in 2000. His research interests include Identity Management, Data Loss Prevention, Network Access Control, Data base Security and Web Security. Sangyong Han is a professor of the school of computer science and engineering, ChungAng University, Seoul, Korea. He received Bachelor of Engineering in College of Engineering from Seoul National University in 1975,