WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Authentication of users

When administrative security is turned on, clients must be authenticated.

If a client tries to access a secured application without being authenticated, an exception is generated.

Table 1 lists typical clients that would invoke WebSphere® ESB components, and the authentication options available for each type of client.
Table 1. Authentication options for various clients
Client Authentication options Notes
Web services clients You can use WS-Security/SOAP authentication.  
Web or HTTP clients HTTP Basic authentication (the browser prompts the client for a user name and password). These clients reference JSPs, Servlets, and HTML documents.
Java™ clients JAAS.  
All clients SSL client authentication.  

Some of the components of the WebSphere ESB 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 ESB 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 ESB installer collects the user name and password for the runAs role.


concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/csec_authentication.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).