IBM Tivoli Access Manager [EOL] Reviews

Vendor: IBM

4.0 out of 5

29 reviews
93% willing to recommend

1,576 followers

What is IBM Tivoli Access Manager [EOL]?

IBM Tivoli Access Manager is a robust and secure centralized policy management solution for e-business and distributed applications. IBM Tivoli Access Manager WebSEAL is a high performance, multi-threaded Web server that applies fine-grained security policy to the Tivoli Access Manager protected Web object space. WebSEAL can provide single sign-on solutions and incorporate back-end Web application server resources into its security policy.

Get the IBM Tivoli Access Manager [EOL] Buyer's Guide and find out what your peers are saying about IBM Tivoli Access Manager [EOL], AlertEnterprise Guardian and more!

Buyer's Guide

IBM Tivoli Access Manager [EOL]

October 2024

Get the report

Helped 814,763 peers since 2012

Featured reviews

Roopesh Verma

Senior Consultant at Symantec

Before solution implemented it took around 2-3 weeks to get all the necessary account information for a new employee in my organization. Since implementation, this now only takes a few minutes. As soon as HR submit all their data the user account is generated and the user gets their username and password. Also, we have many applications and before SSO the users had to remember all the different passwords. We have many legacy applications and they had different password policies that were not always as strong as they should be. Now, however, we have one password for all the applications, and one password policy.

Read full review

it_user228537

Solutions Architect with 1,001-5,000 employees

Several SSO methods are supported out of box. Federation based SSO (SAML / Oauth / OpenID etc) setup is easy. Very good performance and scalability. The internal STS token service can be used for custom SSO tokens. It is highly scalable and can meet high loads and performances. Reverse proxy…

Read full review

it_user238938

Solution Architect Lead at a insurance company with 1,001-5,000 employees

Due to a constraint of the built-in browser in a Handy phone (called NTT i-Mode), the former version of TAM could not be used in the Japan market. The issue was resolved by the decline of Japan-specific Handy phones. Cookies were not supported in i-Mode browser ver.1, which had the highest market share in Japan. Hence, sessions between that browser and WebSEAL could not maintain the session state using a cookie. The constraint had widespread implications. Some examples: re-authentication, session affinity, cookie-based failover mechanisms. Besides, IBM Japan declared that all browsers built in Handy phones were not supported officially in that version. Rather than a weakness of the WebSEAL specification, that constraint was caused by the insufficient i-Mode browser specification, which was developed by NTT Docomo. Considering the negatives, we could not use WebSEAL for Handy-phone facing applications. (A workaround might exist, but the industry-standardized manner of using cookies was in our favor.)

Read full review

Valuable Features

"The integration effort with the end application is quite straightforward and easy."
"OAuth 2 is now the de facto standard for API protection and scoped authorized delegation. IBM TAM now supports OAuth 2 and can act as fully compliant OAuth 2 authorization server."
"The Verify feature: A push method which customers are going for."

Room for Improvement

"Multi-factor authentication with social integration needs to improve."
"An Amazon Machine Image (AMI) for the newer appliance versions for hosting the virtual appliances on AWS will help."
"Looking at their roadmap, they have a broad grasp of the security features which the industry needs."