Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authorizing access to resources > Authorization technology > Authorization providers

Tivoli Access Manager security for WAS

WAS provides embedded IBM Tivoli Access Manager client technology to secure your WAS-managed resources.

The benefits of using Tivoli Access Manager described here are only applicable when Tivoli Access Manager client code is used with the Tivoli Access Manager server:

WAS supports the JACC specification. JACC details the contract requirements for Java EE containers and authorization providers. With this contract, authorization providers can perform the access decisions for resources in Java EE application servers such as WAS. The Tivoli Access Manager security utility that is embedded within WAS is JACC-compliant and is used to:

When applications are deployed, the embedded Tivoli Access Manager client takes any policy and or user and role information stored within the application deployment descriptor or using annotations and stores it within the Tivoli Access Manager Policy Server.

The Tivoli Access Manager JACC provider is also called when a user requests access to a resource that is managed by WAS.

Embedded Tivoli Access Manager client architecture

The previous figure illustrates the following sequence of events:

  1. Users that access protected resources are authenticated using the Tivoli Access Manager login module that is configured for use when the embedded Tivoli Access Manager client is enabled.
  2. The WAS container uses information from the Java EE application deployment descriptor and annotations to determine the required role membership.
  3. WAS uses the embedded Tivoli Access Manager client to request an authorization decision from the Tivoli Access Manager authorization server. Additional context information, when present, is also passed to the authorization server. This context information is comprised of the cell name, Java EE application name, and Java EE module name. If the Tivoli Access Manager policy database has policies specified for any of the context information, the authorization server uses this information to make the authorization decision.
  4. The authorization server consults the permissions that are defined for the specified user within the Tivoli Access Manager-protected object space. The protected object space is part of the policy database.
  5. The Tivoli Access Manager authorization server returns the access decision to the embedded Tivoli Access Manager client.
  6. WAS either grants or denies access to the protected method or resource, based on the decision that is returned from the Tivoli Access Manager authorization server.

At its core, Tivoli Access Manager provides an authentication and authorization framework. We can learn more about Tivoli Access Manager, including the information that is necessary to make deployment decisions, by reviewing the product documentation. The following guides are available in the IBM Tivoli Access Manager for e-business Information Center:

Tivoli Access Manager provides centralized administration of multiple servers.

The previous figure is an example architecture showing WASs secured by Tivoli Access Manager.

The participating WASs use a local replica of the Tivoli Access Manager policy database to make authorization decisions for incoming requests. The local policy databases are replicas of the master policy database. The master policy database is installed as part of the Tivoli Access Manager installation. Having policy database replicas on each participating WAS node optimizes performance when making authorization decisions and provides failover capability.

Although the authorization server can also be installed on the same system as WAS, this configuration is not illustrated in the diagram.

All instances of Tivoli Access Manager and WAS in the example architecture share the LDAP user registry on Machine E.

The LDAP registries that are supported by WAS are also supported by Tivoli Access Manager.

It is possible to have separate WAS profiles on the same host that is configured for different Tivoli Access Manager servers. Such an architecture requires that the profiles are configured for separate Java SE Runtime Environments (JRE 6) and therefore you need multiple JREs installed on the same host.
Authorization providers
IBM Tivoli Access Manager for e-business Information Center


Search Tips   |   Advanced Search