Table of Contents (exploded view)

Enterprise Identity Mapping (EIM)

EIM concepts

EIM registry definition

EIM associations

Identifier associations

Source and target association relationship

Migration considerations

Migration from release to release

Planning for EIM

Identifying skill requirements

Team members

Planning for EIM client applications

Accessing the EIM domain

Setting up EIM on z/OS

Managing registries

Working with registry aliases

Adding a new user

Removing a user

Changing access authority

Using RACF commands to set up and tailor EIM

Storing LDAP binding information in a profile

Optionally setting up a registry name for your local RACF registry

Steps for setting up lookups that do not need a registry name

Ongoing RACF administration

Disabling use of an EIM domain

Steps for disabling use of an EIM domain

Using output from the RACF database unload utility and eimadmin to prime your EIM domain with information

Developing applications

Writing EIM applications

Define a private user registry type in EIM

Building an EIM application

Special considerations for applications that will be shared between different releases of z/OS

Messages

The eimadmin utility

The label line

Processing differences between command-line options and input files

EIM Auditing

What goes into an audit record

Working with audit records

EIM APIs

EimRC -- EIM return code parameter for C/C++

Field descriptions

EIM header file and example

Example for creating LDAP suffix and user objects

Working with remote services

The z/OS Identity Cache

Configuring user ID mapping

Configuring and setting up EIM

Configuring Identity Cache connection defaults

Configuring z/OS sysplex for the Identity Cache

ICTX Java API

/com/ibm/ictx/identitycontext package

Accessing RACF remotely to perform authorization checks and create audit records

Remote auditing requests

SMF Record Type 83 subtype 4 records