Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Operating Service Gateway for IDMS/DB : Implementing External Security

Implementing External Security
The TIBCO Object Service Broker external security interface is used only if:
The TIBCO Object Service Broker external security interface macros for CA‑IDMS Release 12.0 and greater support any external security package used with CA‑IDMS.
Security Process
When the Gateway issues a CA‑IDMS BIND RUN UNIT, CA‑IDMS Exit 14 is initiated. Depending on the setting of the EXTERNALUSERID gateway startup parameter, Exit 14 passes the TIBCO Object Service Broker session ID or the current security group as the user ID to the external security package. Refer to Supplying Service Gateway for IDMS/DB Startup Parameters for more information. The external security package verifies that the user ID is authorized to access the requested subschema or area.
If the TIBCO Object Service Broker external security interface macros are not installed and an external security package (for example, CA-ACF2) is used to verify user IDs against subschemas and/or areas, the user ID that submits the Gateway job requires access (for batch jobs) or the started task name requires access (for started tasks).
Installing the External Security Interface
This process assumes an external security package (such as the CA-ACF2/IDMS interface) is installed and that Exit 14 (in RHDCUXIT) is activated.
CA‑IDMS Release 12 and Greater
If you are installing an external security interface for CA‑IDMS Release 12 or greater, the HRNSEC12 and IDMSS12X TIBCO Object Service Broker macros are located in the MACRO data set. These data sets are distributed with TIBCO Object Service Broker. The HRNSEC12 macro contains instructions for installing both HRNSEC12 and IDMSS12X. IDMSS12X replaces the existing SVC user exit supplied by CA‑IDMS.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved