Authorization providers
WAS supports authorization that is based on the Java Authorization Contract for Containers (JACC) specification in addition to the default authorization.
JACC is a new specification in J2EE 1.4. It enables third-party security providers to manage authorization in the appserver.
When security is enabled in WAS, the default authorization is used unless a JACC provider is specified. The default authorization does not require special setup, and the default authorization engine makes all of the authorization decisions. However, if a JACC provider is configured and set up for WAS to use, all of the enterprise beans and Web authorization decisions are delegated to the JACC provider.
WAS supports security for J2EE applications and also for its administrative components. J2EE applications, such as Web and EJB components are protected and authorized per the J2EE specification. The administrative components are internal to WebSphere Application Server and are protected by the role-based authorizer. The administrative components include the console, MBeans, and other components such as naming and security. For more information on administrative security, see Role-based authorization.
When a JACC provider is used for authorization in WebSphere Application Server, all of the J2EE application-based authorization decisions are delegated to the provider per the JACC specification. However, all administrative security authorization decisions are made by the WAS default authorization engine. The JACC provider is not called to make the authorization decisions for administrative security.
When a protected J2EE resource is accessed, the authorization decision to give access to the principal is the same whether using the default authorization engine or a JACC provider. Both of the authorization models satisfy the J2EE specification, and function the same. Choose a JACC provider only when you want to work with an external security provider such as Tivoli Access Manager. In this instance, the security provider must support the JACC specification and be set up to work with WAS. Setting up and configuring a JACC provider requires additional configuration steps, depending on the provider. Unless you have an external security provider used to with WAS, use the default authorization.
Sub-topics
JACC support in WAS
JACC providers
JACC policy context handlers
JACC policy context identifiers (ContextID) format
JACC policy propagation
JACC registration of the provider implementation classes
Role-based security with embedded Tivoli Access Manager
Tivoli Access Manager integration as the JACC provider
Tivoli Access Manager security for WAS
Related concepts
Authorization technology
Related tasks
Enabling an external JACC provider
Authorizing access to J2EE resources using Tivoli Access Manager
Propagating security policy of installed applications to a JACC provider using wsadmin scripting
Related Reference
Interfaces that support JACC
Security authorization provider troubleshooting tips