Task overview: Securing resources

WebSphere Application Server supports the Java EE model for creating, assembling, securing, and deploying applications. Applications are often created, assembled, and deployed in different phases and by different teams.

We can secure resources in a Java EE environment by following the required high-level steps. Consult the Java EE specifications for complete details.

• Set up and enable security. We must address several issues prior to authenticating users, authorizing access to resources, securing applications, and securing communications. These security issues include migration, interoperability, and installation. After installing WebSphere Application Server, you must determine the proper level of security needed for the environment. For more information, see Set up, enabling and migrating security.

• Configure multiple domains. Security domains enable you to define multiple security configurations for use in our environment. For example, we can define different security (such as a different user registry) for user applications than for administrative applications. We can also define separate security configurations for user applications deployed to different servers and clusters. For more information, see Configure multiple security domains

• Authenticate users. The process of authenticating users involves a user registry and an authentication mechanism. Optionally, we can define trust between WebSphere Application Server and a proxy server, configure single sign-on capability, and specify how to propagate security attributes between application servers. For more information, see Authenticating users.

• Authorize access to resources. WebSphere Application Server provides many different methods for authorizing accessing resources. For example, we can assign roles to users and configure a built-in or external authorization provider. For more information, see Authorizing access to resources.

• Secure communications. WebSphere Application Server provides several methods to secure communication between a server and a client. For more information, see Secure communications.

• Develop extensions to the WebSphere security infrastructure. WebSphere Application Server provides various plug points so that we can extend the security infrastructure. For more information, see Develop extensions to the WebSphere security infrastructure.

• Use the Auditing Facility to report and track auditable events to ensure the integrity of the system. For more information, see Audit the security infrastructure

• Secure various types of WebSphere applications. See Secure WebSphere applications for tasks involving developing, deploying, and administering secure applications, including web applications, web services, and many other types. This section highlights the security concerns and tasks that are specific to each type of application.

• Tune, harden, and maintain security configurations. After we have installed WebSphere Application Server, there are several considerations for tuning, strengthening, and maintaining the security configuration. For more information, see Tuning, hardening, and maintaining security configurations.

• Troubleshoot security configurations. For more information, see Troubleshooting security configurations.

Results

Your applications and production environment are secured.

Example

See the Security: Resources for learning article for more information on the WAS security architecture.

Security: Resources for learning