29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

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.

LDAP is a fast and simple way of looking up user entities in a hierarchical data<br />

structure. It has advantages over using databases as a user repository in terms<br />

of speed, simplicity, and standardized models or schemas for defining data.<br />

Standard schemas have standard hierarchies of objects, such as objects that<br />

represent a person in an organization. These objects, in turn, have attributes<br />

such as a user ID, common name, and so forth. The schema can have custom<br />

objects added to it, meaning that your directory is extensible and customizable.<br />

Generally, LDAP is chosen over a custom database repository of users for these<br />

reasons. LDAP implementations (such as <strong>IBM</strong> Tivoli Directory <strong>Server</strong>) use<br />

database engines under the covers, but these engines are optimized for passive<br />

lookup performance (through indexing techniques). This is possible because<br />

LDAP implementations are based on the assumption that the data changes<br />

relatively infrequently and that the directory is primarily for looking up data rather<br />

than updating data. For more information about <strong>IBM</strong> Tivoli Directory <strong>Server</strong>, see<br />

the following Web page:<br />

http://www.ibm.com/software/tivoli/products/directory-server/<br />

2.2.2 Integration with <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong><br />

You can enable security in <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> to manage users, and<br />

assign specific roles to them. To have a user account repository you must select<br />

the type of user registry to be used (in this case, an LDAP registry). Tivoli<br />

Directory <strong>Server</strong> can be used as a standalone LDAP registry for user account<br />

repository of <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong>. You can configure your user<br />

account repository through the Integrated Solutions Console or through the<br />

wsadmin command line tool.<br />

Security, networking, and topology considerations<br />

Because the LDAP server contains sensitive data in terms of authentication,<br />

authorization, and privacy, the LDAP server belongs to the data layer of the<br />

network. It is suggested to enable SSL options in the <strong>WebSphere</strong> <strong>Application</strong><br />

<strong>Server</strong> security configuration so that the data is encrypted between the<br />

application server layer and the data layer.<br />

Legal considerations (privacy and data protection): There might be some<br />

legal or regulatory issues that surround storing of certain data types, such as<br />

personally identifiable data in the European Union, on IT systems. Ensure that<br />

you have consulted your legal department before deploying such information<br />

on your systems. These considerations vary by geography and industry.<br />

For a list of supported directory servers for <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong>, see<br />

1.4.5, “Directory servers” on page 22.<br />

34 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

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

Saved successfully!

Ooh no, something went wrong!