Using PassTickets in FEPI applications

A FEPI application uses the PassTicket and user ID to perform a sign-on in the back-end system just as if it were sending a password and user ID.

Before you begin

To process PassTickets, the external security manager uses keys, known as Secure Signon keys, that are shared by the front-end and back-end systems. You must define a Secure Signon key for each target system with which FEPI communicates. For information about how to do this with RACF® by defining profiles in the PTKTDATA resource class, see Using the secured signon function in z/OS Security Server RACF Security Administrator's Guide. Users of other ESMs should refer to the documentation for their product.

Procedure

  1. The end user is verified by signing on to the front-end CICS® system in the usual way.
  2. When the end-user runs a transaction that uses FEPI, your application issues a FEPI REQUEST PASSTICKET command to obtain a PassTicket. If EDF is being used, the PassTicket is not displayed. The user ID for which the PassTicket is generated is that of the currently signed-on user. Your FEPI application can use an EXEC CICS ASSIGN command to check the user ID of the currently signed-on user.
  3. Your FEPI application uses the PassTicket and user ID to perform a sign-on in the back-end system. For example:
    EXEC CICS FEPI SEND FORMATTED
                        CONVID(convid) FROM(CESN userid PassTicket)
                        FROMLENGTH(length_of_data)
    It is the application’s responsibility to provide the signon processing, because CICS cannot know either the type of back-end system (CICS or IMS™) or the back-end program being used for signon processing.
  4. The back-end system uses an unchanged interface to perform the sign-on. A CICS system that receives a user ID and a PassTicket can use its existing procedures to sign on the user ID. RACF takes care of the fact that a PassTicket, rather than a password, is passed to it.

Results

If the PassTicket times out (because, for example, of a session failure), your application must generate another and try to sign on again. If sign-on continues to fail and the front-end and back-end are in different MVS™ systems, check that the system clocks are suitably synchronized. Too many failed sign-on attempts could result in the user ID being revoked.

What to do next

For detailed information about PassTickets, see Using the secured signon function in z/OS Security Server RACF Security Administrator's Guide. For information about using RACF with CICS, see .


dfhp75u.html | Timestamp icon Last updated: Sunday, 4 June 2017