The implementation of Pass Ticket support requires customization within both TPX and the security system.
*** For RACF, please confirm all details with IBM. The following is intended as general guidance only.
- Use the PTKTDATA resource class to define profiles that contain the encryption key used for generating and validating Pass Tickets.
- A profile is added for each APPLID that receives sign-ons with Pass Tickets.
- You will define TPX to PTKTDATA as well as any other applications or profiles that will be generating or validating Pass Tickets.
- For RACF information on setting up Pass Tickets, please refer to z/OS Security Server RACF Security Administrator's Guide, and contact IBM.
Bypassing Pass Ticket replay protection:
The option to bypass Pass Ticket replay protection allows the plus-or-minus-10-minute Pass Ticket replay protection to be bypassed for selected applications or combinations of selected applications, users, or groups.
Add the text string NO REPLAY PROTECTION to the APPLDATA field of the PTKTDATA profile.
SETROPTS CLASSACT(PTKTDATA) RACLIST(PTKTDATA)
RDEFINE PTKTDATA applid SSIGNON(KEYMASKED(0123456789ABCDEF)) APPLDATA('NO REPLAY PROTECTION') UACC(NONE)
SETROPTS RACLIST(PTKTDATA) REFRESH
APPLDATA(‘NO REPLAY PROTECTION’)
Allows reuse of the same PassTicket multiple times, in the allowed plus or minus 10 minutes.
Note: The PassTicket 'NO REPLAY PROTECTION' value should only be specified in secure environments where access to generate PassTickets is contained in a secure internal network.
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 based on the settings in CA TPX and the Pass Ticket Profile, if any, as defined in the external security system.
A. Logon to TPX with a Pass Ticket
- Set User Option ' Pass Ticket User: Y ' either in first profile assigned to a user or directly in user level
- To use qualified pass tickets, set ' Qualified PTick User : Y ' either in first profile assigned to a user or directly in user level
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 password 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:
- If the user is passed to another TPX by the Affinity feature, a pass ticket is generated for the TPX that the user is passed to.
- If a signoff command (/F) occurs, it is converted to a logoff. This includes those produced by a timeout.
- Timeouts that would lock the terminal are converted to logoffs.
- The user must supply a lock word when locking the terminal.
B. Logon to applications with a Pass Ticket
- The application must be defined in CA TPX with session data that contains &PSWD or a startup ACL that keys in &PSWD to ensure secured signon using 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.)
- This pass ticket profile name will be supplied to the external security system instead of userid during Pass Ticket generation.
- When Prof name is NOT specified (field left blank), TPX issues the pass ticket request with the USERID & APPLID.
- When Prof name is specified, TPX issues the pass ticket request with the USERID & Prof name.
You can use security traces to verify whether or not your application requires a 'Pass Ticket Prof name' to be defined.
- Run a RACF security trace against the TPX address space to verify the generation of a pass ticket in RACF.
- Repeat the test with a second RACF security trace against the application to verify what entity the application is sending to RACF for validation.
- If it is not the VTAM APPLID, define this entity in the TPX ACT 'Pass Ticket Prof name' field so that TPX requests the pass ticket for this value instead of the APPLID.
- It is important to not run each RACF security trace at the same time so that the trace data remains specific to either TPX or the application.
- Also ensure the entity identified in the trace on the application (the one that you are specifying in 'Pass Ticket Prof name') is defined within RACF PTKTDATA.
- To verify if the profile name has been set up for pass tickets, contact IBM who can advise based upon the information in the RACF security trace.
- If does not exist, you will need to define it, following instructions from IBM.
'Pass Ticket Prof name' is usually required for TSO and VM systems, where this parameter will have the value "TSOsmfid" or "VMcpuid".
- TSO - TSOsmfid
- VM – Vmcpuid
Other applications requiring Pass Ticket prof name, as provided to us by TPX customers: (Please verify for your environment.)
- MVSxxxx system default
- APPLID of application
- SESSIONID >>> Note that this was not the APPLID but rather the SESSIONID defined in TPX.
Additional Setup Requirements:
- SMRT Optional Parameters: Set both of these to Y:
- SMRT Option 030 - This option will cause users defined as Pass Ticket Users to return to the CA TPX logo if a signoff command is entered or generated. Pass Ticket users normally would not see the CA TPX logo because all signoffs are normally converted to logoffs. If a user returns to the CA TPX logo then subsequently signs on with their real password, the signon will not be secured using the Pass Ticket technique.
- SMRT Option 031 - This option will display "Pass Ticket" on the CA TPX menu in the location where "Check Messages" might appear (the W3 variable), if a user is defined as a Pass Ticket User. The "Check Messages"indication temporarily overrides the "Pass Ticket" indication. This option will cause the letters "PTIX" or the words "Pass Ticket" to appear on the menu in the "Status" column, for any application defined as a "Pass Ticket Application". These are the UENTWSTS and UENTWSTL variables, respectively. Other status indicator will temporarily override the Pass Ticket indication.
- SMRT Reserved Options:
Access the SMRT Reserved Options by entering command “OPTIONS” on the SMRT Optional Parameters panel, then scroll down to set these options:
- RsvOpt 041 - When using pass ticket instead of password/phrase to access applications, set RsvOpt 41 to Y to ensure the user-id has been validated through the external security manager (Top Secret/ACF2/RACF) to gain access to TPX. This will handle the case where certain user-ids are set to SECURITY=NONE and should not have a pass ticket generated for them to access an application.
- RsvOpt 042 - (Optional) Set RsvOpt 042 to Y if you need pass ticket generation messages in the TPX log for audit or other site requirements (TPXL0920, TPXL0921, TPXL0922, TPXL0923). These messages are useful during implementation and testing of pass tickets.
To ensure that all changes have been implemented, cycle TPX or use TPXOPER RELOAD for each change.