When security is turned on, clients must be authenticated.
If a client tries to access a secured application without being authenticated, an exception is thrown.
Web clients (for instance JSPs or servlets) can be setup for HTTP Basic authentication, so that when you reference the URL, the browser prompts for a user name and password.
Java clients should use JAAS for authentication.
WebServices clients can use WebServices/SOAP authentication.
Some of the components of the WebSphere Process Server infrastructure have authentication aliases that are used to authenticate the runtime code for access to databases and the messaging engine. These Business Process Choreographer and Common Event Infrastructure authentication aliases are outlined in subsequent topics. The WebSphere Process Server installer collects the user name and passwords to create these aliases.
Some runtime components have message driven beans (MDBs) that are configured with a runAs role. The WebSphere Process Server installer collects the user name and password for the runAs role.
Last updated: Tue Feb 21 17:33:02 2006
(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)