Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment
Authorizing access to resources
WAS provides many different methods for authorizing accessing resources. For example, you can assign roles to users and configure a built-in or external authorization provider. We can create an application, an EJB module, or a web module and secure them using assembly tools.
To authorize user or group access to resources, read the following articles:
- Secure you application during assembly and deployment. For more information on how to create a secure application using an assembly tool, such as the IBM Rational Application Developer, see the information about securing applications during assembly and deployment.
- Authorize access to Java EE resources. WAS supports authorization that is based on the JACC specification in addition to the default authorization. When security is enabled in WAS, the default authorization is used unless a JACC provider is specified. See Authorization providers.
- Authorize access to administrative resources. We can assign users and groups to predefined administrative roles such as the monitor, configurator, operator, administrator, auditor and iscadmins roles. These roles determine which tasks a user can perform in the administrative console. See Authorizing access to administrative roles.
What to do nextAfter authorizing access to resources, configure the Application Server for secure communication. See Secure communications.
Authorizing access to Java EE resources using Tivoli Access Manager
Authorizing access to administrative roles
Fine-grained administrative security
Create a fine-grained administrative authorization group
Edit a fine-grained administrative authorization group
Fine-grained administrative security in heterogeneous and single-server environments
Use SCA authorization and security identity policies
Use the SCA RequestContext.getSecuritySubject() API
Secure applications during assembly and deployment