Comparison of external authentication mechanisms for WebSEAL

What requirements to look for when deciding between the C and HTTP external authentication interfaces

From the developerWorks archives

Chris Choi and Peter Cogill

Date archived: December 13, 2016 | First published: July 31, 2007

This article compares the two supported mechanisms for providing custom authentication services within IBM® Tivoli® Access Manager for e-business (TAMeB) WebSEAL, C and HTTP, and identifies key differences between them. These key differences are used to identify sets of requirements where one approach is more suitable than the other. A reader can then use these differences to determine which approach to use for their custom authentication processing.

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=Tivoli, Sample IT projects
ArticleID=240950
ArticleTitle=Comparison of external authentication mechanisms for WebSEAL
publish-date=07312007