Before you begin
The Java Authorization Contract for Containers (JACC) defines a contract between Java 2 Platform, Enterprise Edition (J2EE) containers and authorization providers. It enables any third-party authorization providers to plug into a J2EE 1.4 application server such as WebSphere Application Server to make the authorization decisions when a J2EE resource is accessed. The JACC provider can be implemented using Tivoli Access Manager.
Steps for this task
Enter the listening ports used by Tivoli Access Manager clients, separated by a comma. If a range of ports is specified, separate the lower and higher values by a colon (:) (for example, 7999, 9990:999).
More than one authorization server can be specified by separating the entries with commas. Specifying more than one authorization server at a time is useful for reasons of failover and performance.
The priority value is determined by the order of the authorization server use (for example, auth_server1:7136:1, and auth_server2:7137:2). A priority value of 1 is required when configuring against a single authorization server.
Enter the name of the Tivoli Access Manager security domain that is used to store WebSphere Application Server users and groups.
If a security domain is not established at the time of the Tivoli Access Manager configuration, leave the value as Default.
What to do next
After you configure a JACC provider, you must enable it in the WebSphere Application Server administrative console. See Enabling an external JACC provider for more information.Related concepts
Tivoli Access Manager integration as the JACC provider
Authorization providers
JACC providers
JACC support in WebSphere Application Server
Related reference
Interfaces that support JACC
Authorization provider troubleshooting tips
External Java Authorization Contract for Containers provider settings