03.05.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS

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

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

Enabling Single Sign-On for <strong>WebSphere</strong><br />

After configuring <strong>WebSphere</strong> Application Server to use Domino LDAP, the SSO<br />

configuration is identical to the one discussed in the previous section. Please<br />

refer to “Enabling Single Sign-On for <strong>WebSphere</strong>” on page 494 for details.<br />

Remember that you should always generate LTPA keys after successful<br />

configuration of the LDAP user registry.<br />

Important: Do not forget to enter the domain name in the Single sign-on<br />

section of the LTPA configuration panel.<br />

Enabling Single Sign-On for Domino<br />

When using Domino directory as a user registry, Domino Server does not need to<br />

use directory assistance as described in the previous section. After putting all the<br />

application users and groups into your Domino directory, you can follow the<br />

instruction from “Enabling Single Sign-On for Domino” on page 499 for importing<br />

LTPA keys and enabling Single Sign-On for the Domino Server.<br />

For our sample scenario, we have defined the following users and groups in<br />

Domino Directory:<br />

Table C-2 Users and groups defined in Domino directory for ITSO application<br />

Group name<br />

managergrp/ITSO<br />

clerkgrp/ITSO<br />

accountantgrp/ITSO<br />

consultantgrp/ITSO<br />

Group members<br />

manager01/ITSO<br />

clerk01/ITSO<br />

accountant01/ITSO<br />

consultant01/ITSO<br />

We have mapped Domino directory groups to corresponding user roles in the<br />

ITSO bank application, and accordingly modified ACL in the<br />

ITSOBankComments application database.<br />

If your server is already configured to use Single Sign-On, please remember that<br />

reconfiguration does not mean creating a new Web Single Sign-On Configuration<br />

document. On a server, it may only be one Web Single Sign-On Configuration<br />

Document. So, if you have one already, you should edit it and import new LTPA<br />

keys.<br />

Testing Single Sign-On<br />

For testing this scenario you can follow testing instructions from the previous<br />

section. Please refer to “Testing Single Sign-On” on page 505.<br />

512 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

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

Saved successfully!

Ooh no, something went wrong!