CA-TPX provides support for Secured Signon using Pass Tickets. The use of Pass Tickets eliminates the transmission of passwords across network facilities in clear text.
A pass ticket is a one-time only password substitute that is automatically generated by an authentication server, such as CA's Single Signon Option or IBM's Network Security Program or on behalf of a client workstation requesting access to a mainframe application, such as TPX.
Once a user is signed on to TPX, Pass Tickets may also be generated for applications subsequently accessed through TPX.
NOTE 1: This document is specific to Top Secret. For instructions specific to ACF2 or RACF, please refer to the links at the end of this document.
NOTE 2: IF PTF LU08678 (enhancement) is applied and active, regardless of whether it is a legacy pass ticket or enhanced pass ticket; TPX
PTF LU03420 (Enhancement) must be applied and active as well.
Component: TPX for Z/OS
The implementation of Pass Ticket (PTKT) support requires customization within both TPX and the security system.
Customize Top Secret for Pass Tickets
For Top Secret, you must have the required NDT rules in place.
Refer to Top Secret User Guide and the Top Secret Cookbook.
1.TSS ADDTO(NDT) PSTKAPPL(applname) SESSKEY(................) SIGNMULTI
2.TSS ADD(dept) PTKTDATA(IRRPTAUT)
The Resource Class has a maximum Ownership of 8 characters.
3.The Resource can be permitted as one of the following, where 'applname' is the
Application Name defined in the NDT and 'userid' is the Userid:
4. And finally, authority to generate pass tickets:
TSS PER(serveracid) PTKTDATA(IRRPTAUTH.applname.acidname) ACCESS(UPDATE)
Authorize Applications to Generate or Evaluate PassTickets
Applications can invoke the R_ticketserv or R_GenSec callable service to generate or evaluate a PassTicket on behalf of an authorized user.
If running 64-bit addressing mode (AMODE 64), you must use R_GenSec. R_ticketserv does not support AMODE 64.
For complete information about R_GenSec and R_ticketserv, see the IBM z/OS Security Server RACF Callable Services documentation.
The PTKTDATA resource class authorizes the use of each callable service.
The following table describes the required resource and access for generating and evaluating PassTickets:
Operation Resource Name Access Required
Generate PassTicket IRRPTAUTH.application.target_ userid UPDATE
Evaluate PassTicket IRRPTAUTH.application.target_ userid READ
Invoking R_ticketserv/R_GenSec triggers a security call for PTKTDATA(IRRPTAUTH.application.target_userid) to ensure the caller is authorized to evaluate/generate a PassTicket.
If the calling ACID (typically the region ACID) is authorized, the PassTicket operation can occur.
If the PTKTDATA class is not active, or the required resources are not defined, the PassTicket request fails.
How to Authorize applications to generate or evaluate PassTickets.
1. Define the PTKTDATA resource to the Resource Descriptor Table (RDT).
TSS ADD(RDT) RESCLASS(PTKTDATA)
A PTKTDATA resource definition now exists in the RDT.
2. Grant ownership of the IRRPTAUT resource:
TSS ADD(owning_acid) PTKTDATA(IRRPTAUT)
IRRPTAUT is now owned.
3. Give a target user the permission to have a PassTicket generated/evaluated through an application:
TSS PER(acid) PTKTDATA(IRRPTAUTH.application.target_userid)
application --- Specifies the application.
target_userid --- Specifies the user who receives the permission.
A permit is added.
4. If control option PTKRESCK(YES) is set, grant additional permissions as follows:
TSS ADD(owning_acid) PTKTDATA(PTKTGEN.)
TSS PER(userid) PTKTDATA(PTKTGEN.application.target-userid)
< See - Authorize Applications to Generate or Evaluate PassTickets STEP :4. for additional details on PTKRESCK >
Top Secret customization for applications to generate or evaluate PassTickets complete.
Within TPX, there are two separate aspects of Pass Ticket support: Users and Applications.
You can implement one or the other or both depending upon your site requirements.
You can specify pass ticket and/or qualified pass ticket for users and applications.
When both are specified, CA TPX attempts to use the most secure form of pass ticket available
as defined in the external security system.
A. TPX customization to activate Pass Ticket.
This parameter does not impact the actual sign on to TPX.
TPX accepts the userid and password then makes a security call for validation.
TPX is unaware of whether the passcode field contains a password or pass ticket at this point.
It is only after the user is signed on to TPX where this parameter becomes important, and these are outlined in the field level help:
B. TPX applications sign-on with a Pass Ticket
Session Options requirements
Set ' Generate Pass Ticket: Y ' in the ACT (Application Characteristics Table), or Profile Session Options, or User Session Options.
To use qualified pass tickets, set ' Gen Qualified Pass Ticket: Y ' in the ACT, or Profile Session Options, or User Session Options.
Set 'Pass Ticket Prof name', if required, in the ACT. (Parameter is not available at profile or user level.)
The 'Pass Ticket Prof name' will be supplied to the external security system instead of userid during Pass Ticket generation.
When 'Pass Ticket Prof name' is NOT specified (field left blank), TPX issues the pass ticket request with the USERID & APPLID.
When 'Pass Ticket Prof name' is specified, TPX issues the pass ticket request with the USERID & Prof name.
NOTE : To use pass ticket in TPX, the 'application' must be defined in CA TPX Application Charateristic table (ACT).
In order to trigger a pass ticket session for a selected application, a startup TPX ACL is required to ensure secured signon.
To verify whether or not your application requires a 'Pass Ticket Prof name' to be defined run the TSS SECTRACE.
For Top Secret (TSS)
Run a SECTRACE against the TPX address space (using TPX jobname) to verify the generation of a pass ticket in TSS.
Repeat the test with a second SECTRACE against the application to verify what is the entity/element the application is sending to TSS for validation.
If it is not the VTAM APPLID, define this entity/element in the TPX ACT 'Pass Ticket Prof name' field to request pass ticket for this value instead of the actual APPLID.
It is important to not run each SECTRACE at the same time so that the trace data remains specific to either TPX or the application.
Also ensure the entity/element identified in the trace on the application (the one that you are specifying in 'Pass Ticket Prof name') is defined within TSS PTKTDATA.
To verify if the profile name has been set up for pass tickets:
TSS LIST(profile_name) DATA(ALL)
'Pass Ticket Prof name' required for TSO and VM systems, will have a value ;
Other applications requiring Pass Ticket prof name, as provided to us by TPX customers: (Please verify for your environment.)
There may be additional applications where this entity/element is required and can be determined in conjunction with the application vendor and your security administrator.
Additional TPX Setup Requirements:
To ensure that all changes have been implemented, it is recommended to re-cycle TPX.
If you are familiar with the reload command that may also be used to implement each change.