Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authorizing access to resources > Authorizing access to Java EE resources using Tivoli Access Manager
Use the built-in authorization provider
We can extend the capabilities of WAS by plugging in your own authorization provider. We can use the built-in authorization or an external JACC authorization provider.
For an explanation of the admin console panels that support these capabilities, see:
Procedure
- Use the built-in authorization provider. IBM recommends that you do not modify any settings on the authorization provider panels if you use the Built-in authorization option. See External authorization provider settings.
- Use an external authorization provider. If you use the External authorization using a JACC provider option, the external providers must be based on the JACC specification to handle the Java EE authorization. By default, WAS enables you to configure the Tivoli Access Manager JACC provider as the default external JACC provider. See External Java Authorization Contract for Containers provider settings and Tivoli Access Manager JACC provider settings.
Related
External authorization provider settings
External Java Authorization Contract for Containers provider settings
Related
Tivoli Access Manager JACC provider settings