FEPI REQUEST PASSTICKET

Request an external security manager to build a PassTicket for a FEPI application.

Syntax

Read syntax diagramSkip visual syntax diagram
FEPI REQUEST PASSTICKET

>>-FEPI REQUEST PASSTICKET--(--data-area--)--------------------->

>--CONVID--(--data-value--)--+--------------------------+------->
                             '-ESMRESP--(--data-area--)-'   

>--+----------------------------+------------------------------><
   '-ESMREASON--(--data-area--)-'   

Description

The FEPI REQUEST PASSTICKET command requests an external security manager (ESM), such as RACF®, to build a PassTicket. The PassTicket is a password substitute that your application can use to sign on to the back-end system associated with the conversation.

The PassTicket that the external security manager generates is for the user ID associated with the task that issues the FEPI REQUEST PASSTICKET command. Use the EXEC CICS ASSIGN command with the USERID option to identify the user ID that is associated with the task.
Note: A request for a PassTicket succeeds if a userid is revoked, but an attempt to sign on with that userid and PassTicket fails.

A PassTicket must be used within 10 minutes of being generated. If the PassTicket times out (because, for example, of a session failure), your application must generate another before attempting to sign on again. Repeated failed sign-on attempts with PassTickets can result in the user ID being revoked.

Your program uses the generated PassTicket and the user ID to perform a sign-on in the back-end system just as if it were sending a password and user ID, as in this example:
EXEC CICS FEPI SEND FORMATTED
                    CONVID(convid) FROM(CESN userid PassTicket)
                    FROMLENGTH(length_of_data)
It is your application’s responsibility to provide the signon processing, because CICS® cannot know either the type of back-end system or the back-end program being used for signon processing.

PassTickets are not displayed when the CICS execution diagnostic facility (EDF) is used.

Before using PassTickets, you must ensure that the system clocks for the target system and the originating system are synchronized to within the valid time range. You must also define a Secure Signon key for each target system. For information on the requirements for using PassTickets, see Generating and using PassTickets for secure sign-on.

Options

CONVID(8-character data-value)
specifies the ID of the conversation with the back-end system for which a PassTicket is required.
ESMREASON(fullword binary data-area)
returns the reason code from the ESM.
ESMRESP(fullword binary data-area)
returns the response code from the ESM. For an explanation of the response and reason codes returned by RACF, see the z/OS Security Server RACF Messages and Codes.
PASSTICKET(8-character data-area)
returns the PassTicket generated by the ESM.

Conditions

The INVREQ condition can have the following RESP2 values:

RESP2
Meaning
240
Conversation ID not owned by this task.
Start of change248End of change
Start of changeThe external security manager does not authorize a request to generate a PassTicket for this region.End of change
249
User not logged on.
250
Passticket not built successfully.
251
CICS ESM interface not initialized.
252
Unknown return code in ESMRESP from the ESM.
253
Unrecognized response from CICS security modules.
254
Function unavailable.


dfhp75q.html | Timestamp icon Last updated: Monday, 5 June 2017