CASECAUT And SCOPE

Products

• Cleanup
• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Top Secret
• Top Secret - LDAP
• Top Secret - VSE

Issue/Introduction

 A type USER ACID was permitted to CASECAUT(TSSCMD.USER.REPLACE.PASSWORD), but when this ACID tried to replace another ACID's password, the following error was received:

 

 	TSS0352E ACID NOT OWNED WITHIN SCOPE

 

 

 

Environment

Release: TOPSEC00200-15-Top Secret-Security
Top Secret r16.0
 

Resolution

Even when using the new class CASECAUT, the administrative rights gained are limited by the scope of the ACID.

I.e. an ACID being type USER only has scope over himself. If the ACID was a DCA, it would have scope over all ACIDs within the department the DCA belongs to.

The CA Top Secret User Guide states:

The CASECAUT resource class to enables users with no administrative authorities to change certain password and issue digital certificate keyring and token commands for users WITHIN THEIR SCOPE.

In order to have no scope limitations the acid needs to be an SCA.