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
The JACC defines a contract between Java EE containers and authorization providers. We can use the default authorization or an external JACC authorization provider. When security is enabled in WAS, the default authorization is used unless a JACC provider is specified.
JACC enables any third-party authorization providers to plug into a Java EE application server (such as WAS) to make the authorization decisions when a Java EE resource is accessed. By default, WAS implements the JACC provider by using Tivoli Access Manager as the external authorization provider.
Read the following articles for more detailed information about JACC before you attempt to configure WAS to use a JACC provider:
Procedure
Related
Use the built-in authorization provider
Enable an external JACC provider
Tivoli Access Manager integration as the JACC provider
Authorization providers
JACC providers
JACC support in WAS
Related
Interfaces that support JACC
Security authorization provider troubleshooting tips
External Java Authorization Contract for Containers provider settings