You can configure a new Java Authentication SPI (JASPI) authentication provider in the cell or in the given security domain by using the administrative console.
This release of WebSphere® Application Server supports integration of message authentication providers that are compliant with the JASPI for Containers Version 1.0 specification.
When JASPI authentication providers are configured, and WebSphere Application Server receives an HTTP request message, the security runtime environment determines if the target application is configured to use JASPI authentication. If so, the runtime environment invokes the selected authentication provider to validate the received message. Otherwise, authentication of the message request is done according to the authentication mechanism provided by WebSphere Application Server for the appropriate messaging layer.
If you want to use JASPI message authentication services, you must supply an implementation of the required interfaces as defined in the JASPI specification. Read Developing a custom JASPI authentication provider for more information on these interfaces.
Authentication of HTTP request and response messages destined for JASPI-enabled deployed applications is performed according to the requirements of the Servlet Container Profile specified in the new specification.
To configure a new JASPI authentication provider using the administrative console, do the following:
You can also configure a new JASPI authentication provider by using wsadmin commands. Read JaspiManagement command group for the AdminTask object for more information.
Verify that your server has been restarted so that the changes to configure the JASPI provider will take effect.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |