Task overview: Secure resources
Procedure
- Set up and enable security.
You must address several issues prior to...
- authenticating users
- authorizing access to resources
- securing applications
- securing communications
These security issues include...
- migration
- interoperability
- installation
- Authenticate users.
The process of authenticating users involves a user registry and an authentication mechanism. Optionally, you can...
- Define trust between WAS and a proxy server
- Configure single sign-on capability
- Specify how to propagate security attributes between appservers
- Authorize 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.
- Secure communications.
WAS provides several methods to secure communication between a server and a client.
- Develop extensions to the WebSphere security infrastructure.
WAS provides various plug points so that you can extend the security infrastructure.
- Secure various types of WebSphere 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 you have installed WAS, there are several considerations for tuning, strengthening, and maintaining your security configuration.
- Troubleshoot security configurations.
Set up and enable security
Authenticate users
Authorize access to resources
Secure communications
Develop extensions to the WebSphere security infrastructure
Tune, harden, and maintain
Troubleshoot security configurations Security: Resources for learning