Customizing security processing
This topic describes the interface between CICS® and RACF® interface, and how you can customize security processing using RACF exit programs.
- Overview of the CICS-RACF interface
- The MVS router
The system authorization facility (SAF) provides your installation with centralized control over security processing by using a system service called the MVS™ router. The MVS router provides a common system interface for all products providing and requesting resource control. - How ESM exit programs access CICS-related information
When CICS invokes the ESM, it passes information about the current CICS environment, for use by an ESM exit program, in an installation data parameter list. How your exit programs access the installation data parameter list depends on whether or not your ESM is RACF. - Using early verification processing
The CICS signon routine invokes the SAF interface, using the RACROUTE REQUEST=VERIFY macro with the ENVIR=VERIFY option in problem-program state. Invoking this version of the macro has no effect if the ESM is RACF, but other external security manager products can get control through the SAF exit interface, and perform their own early verification routine. - CICS security control points
CICS uses RACROUTE macros and RACF callable services to call the external security manager (ESM). Theses calls are issued at a number of control points. Some calls might not always be issued, because CICS reuses entries for eligible user IDs that have already signed on in the CICS region. - Determining the userid of the CICS region
- Specifying user-defined resources to RACF
- Designing applications to use the user-defined resources
This topic gives an example of how you might design applications to make use of the user-defined resources. - Suppressing attach checks for non-terminal transactions
dfht55h.html |
Last updated: Sunday, 4 June 2017