100 lines
6.2 KiB
HTML
100 lines
6.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Develop an EIM identifier naming plan" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalv_id_map_plan.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzalv_identifier_plan" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Develop an EIM identifier naming plan</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalv_identifier_plan"><a name="rzalv_identifier_plan"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Develop an EIM identifier naming plan</h1>
|
||
|
|
<div><p>When planning your Enterprise Identity Mapping (EIM) identity
|
||
|
|
mapping needs, you can create unique <a href="rzalveservereimid.htm#rzalveservereimid">EIM identifiers</a> for users of EIM-enabled applications
|
||
|
|
and operating systems in your enterprise when you want to create one-to-one
|
||
|
|
mappings between user identities for a user. By using identifier associations
|
||
|
|
to create one-to-one mappings you can maximize the password management benefits
|
||
|
|
that EIM provides. </p>
|
||
|
|
<p>The naming plan that you develop depends on your business needs and preferences;
|
||
|
|
the only requirement for EIM identifier names is that they be unique. Some
|
||
|
|
companies may prefer to use each person's full, legal name; other companies
|
||
|
|
may prefer to use a different type of data, such as each person's employee
|
||
|
|
number. If you want to create EIM identifier names based on each person's
|
||
|
|
full name, you may anticipate possible name duplication. How you handle potential
|
||
|
|
duplicate identifier names is a matter of personal preference. You may want
|
||
|
|
to handle each case manually by adding a predetermined character string to
|
||
|
|
each identifier name to ensure uniqueness; for example, you might decide to
|
||
|
|
add each person's department number. </p>
|
||
|
|
<p>As part of developing an EIM identifier naming plan, you need to decide
|
||
|
|
on your overall <a href="rzalv_id_map_plan.htm#id_map_plan"> identity
|
||
|
|
mapping plan</a>. Doing so can help you to decide when you need to be using
|
||
|
|
identifiers and identifier associations versus using policy associations for
|
||
|
|
mapping identities within your enterprise. To develop your EIM identifier
|
||
|
|
naming plan, you can use the work sheet below to help you gather information
|
||
|
|
about the user identities in your organization and to plan EIM identifiers
|
||
|
|
for the user identities. The work sheet represents the kind of information
|
||
|
|
the EIM administrator needs to know when he creates EIM identifiers or policy
|
||
|
|
associations for the users of an application. </p>
|
||
|
|
<div class="p">
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 1. Example EIM identifier planning
|
||
|
|
work sheet</caption><thead align="left"><tr><th align="left" valign="top" width="33.33333333333333%" id="d0e33">Unique identifier name</th>
|
||
|
|
<th valign="top" width="33.33333333333333%" id="d0e35">Identifier or user identity description </th>
|
||
|
|
<th valign="top" width="33.33333333333333%" id="d0e37">Identifier alias</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="33.33333333333333%" headers="d0e33 ">John S Day</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e35 ">Human resources manager</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e37 ">app_23_admin</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="33.33333333333333%" headers="d0e33 ">John J Day</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e35 ">Legal Department</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e37 ">app_xx_admin</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="33.33333333333333%" headers="d0e33 ">Sharon A. Jones</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e35 ">Order Department Administrator</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e37 "> </td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<p>An application that is written to use EIM may specify an alias that it
|
||
|
|
uses to find the appropriate EIM identifier for the application, which the
|
||
|
|
application may use in turn to determine a specific user identity to use.
|
||
|
|
You need to check the documentation for your applications to determine whether
|
||
|
|
you need to specify one or more aliases for the identifier. The EIM identifier
|
||
|
|
or user identity description fields are free form and can be used to provide
|
||
|
|
descriptive information about the user. </p>
|
||
|
|
<p>You do not need to create EIM identifiers for all members of your enterprise
|
||
|
|
at one time. After creating an initial EIM identifier and using it to test
|
||
|
|
your EIM configuration, you can create additional EIM identifiers based on
|
||
|
|
your organization's goals for using EIM. For example, you can add EIM identifiers
|
||
|
|
on a departmental or area basis. Or, you can add EIM identifiers as you deploy
|
||
|
|
additional EIM applications. </p>
|
||
|
|
<p>After you gather the information that you need to develop an EIM identifier
|
||
|
|
naming plan, you can <a href="rzalv_plan_assocs.htm#rzalv_plan_assocs">plan associations</a> for your user identities.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalv_id_map_plan.htm">Develop an identity mapping plan</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|