Securing a composite business service delivered as a software-as-a-service, Part II, Supporting identity propagation (enterprise and federated SSO) and authorization

Using Tivoli Access Manager and Tivoli Federated Identity Manager

From the developerWorks archives

Indrajit Poddar, Min Li, Qiang Wang, Zhi Gan, and Ying Chun Guo

Date archived: December 19, 2016 | First published: September 27, 2007

A composite business service (CBS) introduces many new challenges for security in an SOA solution. In this two-article series, a few security scenarios are examined in a proof-of-concept (PoC) CBS software-as-a-service (SaaS) application for banking called Jivaro. These scenarios help to identify when and how to apply different IBM Tivoli security products. In particular, scenarios for using IBM® Tivoli® Access Manager and Tivoli Federated Identity Manager (TFIM) for meeting SSO requirements in a CBS are described.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Security, Tivoli
ArticleID=254798
ArticleTitle=Securing a composite business service delivered as a software-as-a-service: Part II, Supporting identity propagation (enterprise and federated SSO) and authorization
publish-date=09272007