13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

WSLogin {com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxyrequired delegate=com.ibm.ws.security.common.auth.module.WSLoginModuleImpl;};The example above tells the JVM which is the login module for the WSLoginalias. The Java code in the application will refer to this alias to invoke the loginmodule defined for JAAS.There is another configuration file provided for the Java clients, thewsjaas_client.conf file under the \properties directory.10.7.2 J2C Authentication data entriesJ2C Authentication data entries provide an easy way of administering user nameand password pairs for authentication purposes for any resources in <strong>WebSphere</strong>Application Server V5. These entries are associated with alias names, where thealias names can be used in the resource definitions to refer to a certain username and password pair.The following steps will explain how to set up a J2C Authentication Data Entryusing the Administrative Console.1. Click <strong>Security</strong> -> JAAS Configuration -> J2C Authentication Data.2. When you click New, the page will appear; specify the user ID and passwordthat may be used by Java 2 Connector or <strong>WebSphere</strong> Application Server<strong>V5.0</strong> DataSource.3. Each user ID and password set is identified by a unique alias name. Enteritsobankds_auth as the alias, dbuser as the user ID and password as thepassword.Chapter 10. Administering <strong>WebSphere</strong> security 257

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!