Chapter 17. Single sign-on 429
Figure 17-18 Secured WebSphere administrative console logon window
17.7 Verification
You have completed the configuration in IBM Directory Server Version 5.1, IBM
WebSphere Application Server V5.0 and IBM Content Manager Server V8.2.
Now, log on to eClient and see how it works differently.
1. Open a command window on the eClient server machine.
2. Run the command cd C:\WebSphere\AppServer\bin.
3. Run the command serverstatus -all. This command lists all available
WebSphere servers and their running status.
4. If WebSphere server eClient_Server has not been started, enter the
command startServer eClient_Server to start it.
5. Open a browser and enter the following URL to launch eClient:
http://<eClientHostname>/eClient82/IDMInit
6. The following Network logon window is opened. See Figure 17-19 on
page 430.
430 eClient 101 Customization and Integration
Figure 17-19 Network logon window
7. Enter the user name cn=john,ou=accounting,o=ibm,c=us and password
password.
8. Click OK to log on to WebSphere Application Server. You have to enter the
user name and password only once to log on to WebSphere Application
Server if you have multiple applications with single sign-on enabled.
9. The eClient logon window is displayed. The user name has been taken from
the user credentials in WebSphere Application Server and inserted in the
User ID field. Note that the user ID and password fields are disabled. You are
not allowed to enter data in these two fields.
10.Click Logon to log on to eClient.
If you also installed the WebSphere Portal Server, the logon attempt to the
WebSphere Portal Server with the same user name at this time would not require
entering a password again.

Get eClient 101 Customization and Integration now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.