Tivoli Access Manager JACC provider configuration

You can configure the Java™ Authorization Contract for Containers (JACC) provider for Tivoli® Access Manager to deliver authentication and authorization protection for your applications or for authentication only. Most deployments that use the JACC provider for Tivoli Access Manager to configure Tivoli Access Manager provide both authentication and authorization functionality.

If you want Tivoli Access Manager to provide authentication, but leave authorization as part of WebSphere® Application Server's native security, add the com.tivoli.pd.as.amwas.DisableAddAuthorizationTableEntry=true property to the amwas.amjacc.template.properties file. The file is located in the profile_root/config/cells/cell_name directory.

After this property is set, perform the tasks for setting Tivoli Access Manager Security, as documented.

You can configure the JACC provider for Tivoli Access Manager using either the WebSphere Application Server administrative console or the wsadmin command-line utility.

For details on configuring the JACC provider for Tivoli Access Manager using the administrative console, refer to Configuring the JACC provider for Tivoli Access Manager using the administrative console.
For details on configuring the Tivoli Access Manager JACC provider using the wsadmin command line utility, refer to Configuring the JACC provider for Tivoli Access Manager using the wsadmin utility.

[AIX Solaris HP-UX Linux Windows] [z/OS] The JACC configuration files for Tivoli Access Manager that are common across multiple WebSphere Application Server profiles are created by default under the java/jre directory. When you install WebSphere Application Server, you are given permissions to read and write to the files in this directory.

[AIX HP-UX Solaris] Profiles created by users who are different to the user that installed the application have read-only permissions for this directory.

[AIX Solaris HP-UX Linux Windows] [z/OS] This situation is not ideal because configuration of the JACC provider for Tivoli Access Manager fails in these situations. To avoid this situation, you can add the following property to the profile_root/config/cells/cell_name/amwas.amjacc.template.properties file: com.tivoli.pd.as.jacc.CommonFileLocation=new location where new location is a fully qualified directory name.

[AIX Solaris HP-UX Linux Windows] [z/OS] This property applies read and write permissions to the java/jre directory.

The JACC configuration files are not common across multiple WebSphere Application profiles. The following property setting is added to the profile_root/config/cells/cell_name/amwas.amjacc.template.properties file to specify the location of the JACC configuration for each profile.

com.tivoli.pd.as.jacc.CommonFileLocation=USER_INSTALL_ROOT/etc/pd

The wsadmin command is available to reconfigure the Java Authorization Contract for Containers (JACC) Tivoli Access Manager interface:

$AdminTask reconfigureTAM -interactive

This command effectively prompts you through the process of unconfiguring the interface and then reconfiguring it.