127 lines
8.8 KiB
HTML
127 lines
8.8 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="EIM identifier" />
|
||
|
|
<meta name="abstract" content="This information explains how to create identifiers for a user or an entity within your enterprise." />
|
||
|
|
<meta name="description" content="This information explains how to create identifiers for a user or an entity within your enterprise." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalveservercncpts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalveserverdomain.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="rzalveservereimid.dita" />
|
||
|
|
<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>EIM identifier</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalveservereimid.dita"><a name="rzalveservereimid.dita"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">EIM identifier</h1>
|
||
|
|
<div><p>This information explains how to create identifiers for a user
|
||
|
|
or an entity within your enterprise.</p>
|
||
|
|
<p>An Enterprise Identity Mapping (EIM) <em>identifier</em> represents a person
|
||
|
|
or entity in an enterprise. A typical network consists of various hardware
|
||
|
|
platforms and applications and their associated user registries. Most platforms
|
||
|
|
and many applications use platform-specific or application-specific user registries.
|
||
|
|
These user registries contain all of the user identification information for
|
||
|
|
users who work with those servers or applications.</p>
|
||
|
|
<p>You can use EIM to create unique EIM identifiers for people or entities
|
||
|
|
in your enterprise. You can then create identifier associations, or one-to-one
|
||
|
|
identity mappings, between the EIM identifier and the various user identities
|
||
|
|
for the person or entity that the EIM identifier represents. This process
|
||
|
|
makes it easier to build heterogeneous, multiple-tier applications. It also
|
||
|
|
becomes easier to build and use tools that simplify the administration involved
|
||
|
|
with managing every user identity that a person or entity has within the enterprise.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">EIM identifier representing a person</h4><p>Figure 3 shows
|
||
|
|
an example of an EIM identifier that represents a person named <em>John Day</em> and
|
||
|
|
his various user identities in an enterprise. In this example, the person <em>John
|
||
|
|
Day</em> has five user identities in four different user registries: <samp class="codeph">johnday</samp>, <samp class="codeph">jsd1</samp>, <samp class="codeph">JOHND</samp>, <samp class="codeph">jsday</samp>, and <samp class="codeph">JDay</samp>.</p>
|
||
|
|
<p><strong>Figure 3:</strong> The relationship
|
||
|
|
between the EIM identifier for <em>John Day</em> and his various user identities</p>
|
||
|
|
<p><br /><img src="rzalv508.gif" alt="Example of an EIM identifier that represents a person" /><br /></p>
|
||
|
|
<p>In EIM, you can create associations that
|
||
|
|
define the relationships between the <samp class="codeph">John Day</samp> identifier
|
||
|
|
and each of the different user identities for <em>John Day</em>. By creating
|
||
|
|
these associations to define these relationships, you and others can write
|
||
|
|
applications that use the EIM APIs to look up a needed, but unknown, user
|
||
|
|
identity based on a known user identity.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">EIM identifier representing an entity</h4><p>In addition
|
||
|
|
to representing users, EIM identifiers can represent entities within your
|
||
|
|
enterprise as Figure 4 illustrates. For example, often the print server function
|
||
|
|
in an enterprise runs on multiple systems. In Figure 4, the print server function
|
||
|
|
in the enterprise runs on three different systems under three different user
|
||
|
|
identities of <samp class="codeph">pserverID1</samp>, <samp class="codeph">pserverID2</samp>, and <samp class="codeph">pserverID3</samp>.</p>
|
||
|
|
<p><strong>Figure
|
||
|
|
4:</strong> The relationship between the EIM identifier that represents the print
|
||
|
|
server function and the various user identities for that function</p>
|
||
|
|
<p><br /><img src="rzalv509.gif" alt="Example of an EIM identifier that represents the print server function" /><br /></p>
|
||
|
|
<p>With EIM, you can create
|
||
|
|
a single identifier that represents the print server function within the entire
|
||
|
|
enterprise. As the example shows, the EIM identifier <samp class="codeph">Print server
|
||
|
|
function</samp> represents the actual print server function entity in the
|
||
|
|
enterprise. Associations are created to define the relationships between the
|
||
|
|
EIM identifier (<samp class="codeph">Print server function</samp>) and each of the user
|
||
|
|
identities for this function (<samp class="codeph">pserverID1</samp>, <samp class="codeph">pserverID2</samp>,
|
||
|
|
and <samp class="codeph">pserverID3</samp>). These associations allow application developers
|
||
|
|
to use EIM lookup operations to find a specific print server function. Application
|
||
|
|
providers can then write distributed applications that manage the print server
|
||
|
|
function more easily across the enterprise.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">EIM identifiers and aliasing</h4><p>EIM identifier
|
||
|
|
names must be unique within an EIM domain. Aliases can help address situations
|
||
|
|
where using unique identifier names can be difficult. An example of the usefulness
|
||
|
|
of EIM identifier aliases is in situations where someone's legal name is different
|
||
|
|
from the name that person is known as. For example, different individuals
|
||
|
|
within an enterprise can share the same name, which can be confusing if you
|
||
|
|
are using proper names as EIM identifiers. </p>
|
||
|
|
<p>Figure 5 illustrates an
|
||
|
|
example in which an enterprise has two users named <em>John S. Day</em>. The
|
||
|
|
EIM administrator creates two different EIM identifiers to distinguish between
|
||
|
|
them: <samp class="codeph">John S. Day1</samp> and <samp class="codeph">John S. Day2</samp>. However,
|
||
|
|
which <em>John S. Day</em> is represented by each of these identifiers is not
|
||
|
|
readily apparent.</p>
|
||
|
|
<p><strong>Figure 5:</strong> Aliases for two EIM identifiers based
|
||
|
|
on the shared proper name <em>John S. Day</em> </p>
|
||
|
|
<p><br /><img src="rzalv511.gif" alt="Example of aliases for EIM identifiers" /><br /></p>
|
||
|
|
<p>By using aliases, the
|
||
|
|
EIM administrator can provide additional information about the individual
|
||
|
|
for each EIM identifier. Each EIM identifier can have multiple aliases to
|
||
|
|
identify which <em>John S. Day</em> the EIM identifier represents. For example,
|
||
|
|
the additional aliases might contain each user's employee number, department
|
||
|
|
number, job title, or other distinguishing attribute. In this example, an
|
||
|
|
alias for <samp class="codeph">John S. Day1</samp> might be <samp class="codeph">John Samuel Day</samp> and
|
||
|
|
an alias for <samp class="codeph">John S. Day2</samp> might be <samp class="codeph">John Steven Day</samp>.</p>
|
||
|
|
<p> You
|
||
|
|
can use the alias information to aid in locating a specific EIM identifier.
|
||
|
|
For example, an application that uses EIM may specify an alias that it uses
|
||
|
|
to find the appropriate EIM identifier for the application. An administrator
|
||
|
|
can add this alias to an EIM identifier so that the application can use the
|
||
|
|
alias rather than the unique identifier name for EIM operations. An application
|
||
|
|
can specify this information when using the Get EIM Target Identities from
|
||
|
|
the Identifier <samp class="codeph">(eimGetTargetFromIdentifier())</samp> API to perform
|
||
|
|
an EIM lookup operation to find the appropriate user identity it needs. </p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalveservercncpts.htm" title="Use this information learn about important EIM concepts that you need to understand to implement EIM successfully.">Enterprise Identity Mapping concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzalveserverdomain.htm" title="This information explains how to use a domain to store all your identifiers.">EIM domain</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|