Authorization providers settings

 

+

Search Tips   |   Advanced Search

 

Use this page to enable a Java Authorization Contract for Containers (JACC) provider for authorization decisions.

To view this administrative console page, click...

Security | Global security | Authorization providers

WebSphere Application Server provides a default authorization engine that performs all of the authorization decisions. In addition, WAS also supports an external authorization provider using the JACC specification to replace the default authorization engine for J2EE applications.

JACC is part of the J2EE specification, which enables third-party security providers such as Tivoli Access Manager to plug into WAS and make authorization decisions.

Important: Unless you have an external JACC provider or want to use a JACC provider for Tivoli Access Manager that can handle J2EE authorizations based on JACC, and it is configured and set up to be used with WAS, do not enable External authorization using JACC.

 

External JACC provider

Use this link to configure WAS to use an external JACC provider. For example to configure an external JACC provider, the policy class name and the policy configuration factory class name are required by the JACC specification.

The default settings contained in this link are used by Tivoli Access Manager for authorization decisions. If you intend to use another provider, modify the settings as appropriate.

 

Configuration tab

Default authorization

This option should be used all the time unless you want an external security provider such as the Tivoli Access Manager to perform the authorization decision for J2EE applications based on the JACC specification.

Default: Enabled

External authorization using a JACC provider

Enable this option only when you plan to use an external security provider such as the Tivoli Access Manager for performing authorization decisions for J2EE applications using the JACC specification.

To use an external provider, complete the following steps:

  1. Configure your JACC provider.

  2. Verify that the required provider implementation classes are in the class path for each WAS process.

    This step is not required when you use Tivoli Access Manager because the application server already contains the implementation classes.

  3. Enable the option...

    External authorization using a JACC provider

  4. Enter the appropriate properties for the provider under the External JACC provider link, which is located under Related Items.

Default: Disabled