In CICS®,
identification can be accomplished in several ways:
- The client can supply a user ID directly. Typically this is done as part
of the authentication process.
You can identify users in this way when
you use basic authentication with the HTTP and ECI application protocols.
- The client can supply information other than a user ID (for example, an
SSL client certificate) during the authentication process. The information
is mapped to a user ID in the security manager.
You can identify users
in this way when you use SSL client certificate authentication with the HTTP
and IIOP application protocols.
- An intermediate server can establish the identity of the
client, and pass it to the client. You can identify users in this way when
you use asserted identity authentication with the IIOP application protocol.
- The user ID can be supplied in a user-replaceable program which is invoked
for each inbound request.
In the HTTP application protocol, the analyzer
program can supply a user ID.
In the IIOP protocol, the program specified
in the URM attribute of the TCPIPSERVICE resource
definition can supply a user ID.
The user ID can be supplied in a URIMAP definition for an
inbound request. You can identify users in this way when you use URIMAP definitions
to handle requests on the HTTP application protocol.
If you do not use one of these methods to supply a user ID, the
default user ID is used.