Response security enables you to define security for individual application functions. To implement response security, you enter a number in the Security class field of the ADSA Response Definition screen. When the application is compiled, the application load module includes the activity number of each response.
At runtime, response security is enforced if the security administrator has secured activities and has defined activities that correspond to the application functions for which response security is defined. When the application issues a security check on a response, CA IDMS central security looks for an activity definition in which the application name matches the CA ADS application name and the activity number matches the CA ADS response security class.
CA ADS makes no calls to CA IDMS central security for security class 0, which is defined always as unsecured.
Note: For more information on defining and controlling application activities, see the CA IDMS Security Administration Guide.
If a user without execute authority for the corresponding activity, attempts to execute a secured response, the runtime system redisplays the screen from which the response was selected, along with the following message:
UNACCEPTABLE RESPONSE. PLEASE TRY AGAIN
Because the response is secured, the function invoked by the response cannot be accessed unless the security administrator has authorized the appropriate users to execute the corresponding application activity defined to CA IDMS central security.
Response security is complemented by the CA ADS security-tailored menus feature. At runtime, security-tailored menus list only those responses that the user has authority to select. Menus are security-tailored by selecting option 2, Security tailored, on the second page of the ADSA General Options screen.
|
Copyright © 2014 CA.
All rights reserved.
|
|