
ISSE 2006 Securing Electronic Business Processes
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
Prof. Dr. Norbert Pohlmann is Professor for System and Information Security at the University of Applied Sciences in Gelsenkirchen, Germany.
Prof. Dr. Helmut Reimer is Chief Executive Officer of TeleTrusT, Germany.
More details
Other editions
Additional editions

Persons
Prof. Dr. Norbert Pohlmann is Professor for System and Information Security at the University of Applied Sciences in Gelsenkirchen, Germany.
Prof. Dr. Helmut Reimer is Chief Executive Officer of TeleTrusT, Germany.
Content
Heather Hinton Mark Vandenwauver
IBM Software Group {hhinton mvanden}@us.ibm.com
Abstract
"I dont see that [federation identity] happening this year, I dont see it happening next year or the year after that~that leaves 2009, and Ill leave that one open ... There are a lot of issues, but basically it boils down to trust and antitrust." [Penn06]. Despite this pessimism, federation technology and models are being deployed and are in production now, only not in those areas that they were originally expected. In this paper, we describe several adoption patterns that we have observed and the characteristics that have driven these deployments. Existing business relationships between companies are often strong enough to support federated relationships and are being used as the foundation of present-day federated identity deployments.
1 Introduction
Federation has typically been cast as the "next best thing" to happen to a users online experience. For example, the much-hyped travel agency example has been used to illustrate the benefits of a federation relationship - when booking travel tickets with an online travel agency, John can seamlessly access the airline (to book seats and identify special requirements), the car rental agency and the hotel. Another equally well discussed example is based on the Internet Service Provider as w/r-Identity Provider, allowing Jane to authenticate to her ISP and then engage in online shopping. These examples, while excellent for explaining some of the values of a federated single sign-on environment, do not yet have widespread adoption, leading many to question if, not even when, federation technology will be adopted.
What is interesting with these early examples of (hypothetical) federation adoption is that they all describe scenarios where federated technology is used to bootstrap a business relationship between companies. It helped, of course, that the average Internet user could immediately see the value of this type of environment. What hurt, however, is that it was not immediately obvious to the federation partners what value they would realize with this environment, if they acted in any role other than an Identity Provider. And given that they all act as Identity Providers right now, why would they willingly give that up? This leads to the conclusion that federation technology can not (and should not) be driving federation adoption in and of itself.
Our customer experience shows us that federation technology and models are being adopted right now though. Federated technology is being adopted in many environments between companies with existing business relationships. Adoption is taking place where there is a need for tighter integration achieved through the loose coupling offered by federation. The adoption/deployment of federated identity solutions that we have been involved with (to date), have all been based on scenarios where:
Business agreements are already in place upon which a federation-driven trust relationship can be based, and,
One of the participants is a clear "owner" of the user identities and is responsible for the identity lifecycle management
System requirements
File format: PDF
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use the free software Adobe Reader, Adobe Digital Editions, or any other PDF viewer of your choice (see eBook Help).
- Tablet/Smartphone (Android; iOS): Install the free app Adobe Digital Editions or another reading app for eBooks, e.g., PocketBook (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.