Enable an external JACC provider

Use this topic to enable an external JACC provider using the administrative console.

The Java Authorization Contract for Containers (JACC) defines a contract between J2EE containers and authorization providers. This contract 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.

Procedure

1. From the WebSphere Application Server administrative console, click Security > Secure administration, applications, and infrastructure > External authorization providers.

2. Under Related items, click External JACC provider.

3. The fields are set for Tivoli Access Manager by default. If you do not plan to use Tivoli Access Manager as the JACC provider, replace these fields with the details for your own external JACC provider.

4. If any custom properties are required by the JACC provider, click Custom properties under Additional properties and enter the properties. When using the Tivoli Access Manager, use the Tivoli Access Manager properties link instead of the Custom properties link. For more information, see Configuring the JACC provider for Tivoli Access Manager using the administrative console.

5. On the External authorization providers panel, select the External authorization using a JACC provider option and click OK.

6. Complete the remaining steps to enable security. If you are using Tivoli Access Manager, select LDAP as the user registry and use the same LDAP server. For more information on configuring LDAP registries, see Configuring Lightweight Directory Access Protocol user registries.

7. Verify that all of the changes are synchronized across all nodes. For more information, see Synchronizing nodes with the wsadmin tool

8. In a multinode environment, stop and start the deployment manager configuration. Issue the following commands on the Qshell command line:

   profile_root/bin/stopManager 
    -username user_name 
    -password password
   
   
   
   profile_root/bin/startManager
   

9. Restart all servers to make these changes effective.

Related concepts

Related tasks

Related Reference