In general terms: How does PassTicket support work in SOLVE:Access 5.0?

Products

• SOLVE:Operations Automation
• SOLVE:Access Session Management
• SOLVE:FTS
• SOLVE

Issue/Introduction

What are the general characteristics for PassTicket support in SOLVE:Access 5.0?

Environment

Release: 5.0 
Component: SOLVE:Access-Session Management

Resolution

The method used in SOLVE:Access 5.0 only requires that the DEFLOGON be updated to include a new parameter indicating that a PassTicket should be used

for the application.

 

When this is found, we make the call to generate the ticket.  If the PassTicket is not generated, an error message is presented, and the session does not start.

 

During session start/logon, the &USERPW variable will return the PassTicket value or the user password, dependent on the value set in the DEFLOGON.

 

 

Regarding nonqualified vs. qualified PassTickets, we only support qualified PassTickets.  Nonqualified passes only the application name on the

generate request, and this is not as secure as qualified, where the userID is passed as the qualifier.

 

Also, according to the SOLVE:Access 5.0 documentation:  The current method of generating PassTickets using the MAIEX02 exit remains

 

valid; however, the distributed sample no longer contains the PassTicket generation code.  If you switch to using the new method,

 

replace .PASSTKT in the logon string with &USERPW.

Additional Information

SOLVE:Access 5.0 tech docs bookshelf current location is:

 

https://techdocs.broadcom.com/us/en/ca-mainframe-software/intelligent-operations/ca-solve-access-session-management/5-0.html