Authorizing access to Java EE resources using Tivoli Access Manager
The Java™ Authorization
Contract for Containers (JACC) defines a contract between Java Platform, Enterprise Edition (Java EE) containers and authorization providers. ![[AIX Solaris HP-UX Linux Windows]](../images/ngdist.svg)
![[IBM i]](../images/ngibmi.svg)
You can use the default authorization or an
external JACC authorization provider.![[z/OS]](../images/ngzos.svg)
You can
use the default authorization, a System Authorization Facility (SAF)
authorization, or an external JACC authorization provider. When
security is enabled in WebSphere® Application
Server, the default authorization is used unless a JACC provider is
specified.
Before you begin
JACC enables any third-party authorization providers to plug into a Java EE application server (such as WebSphere Application Server) to make the authorization decisions when a Java EE resource is accessed. By default, WebSphere Application Server 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 WebSphere Application Server to use a JACC provider: