Implementing IPIC security

These topics tell you how to implement security for IPIC connections.

IPIC bind-time security
A security check can be applied when a request to establish a connection is received from, or sent to, a remote system. This is called bind-time security. Its purpose is to prevent an unauthorized system from connecting to CICS®.
IPIC link security
Link security restricts the resources a user can access, depending on the remote system from which they are accessed. The practical effect of link security is to prevent a remote user from attaching a transaction or accessing a resource for which the link user ID has no authority.
IPIC user security
User security causes a second check of the received security context that flows from the requestor and under which the transaction operates. The received security context usually contains the user ID of the user running the client.
IPIC transaction, resource, and command security
CICS routing transaction, CRTE
You can use the CICS routing transaction, CRTE, with IPIC, LU6.2, or MRO links to run transactions that are on a connected remote system, instead of defining these transactions as remote in the local system.
Security checking done in AOR with IPIC
This depends on how LINKAUTH, SECURITYNAME and USERAUTH are specified in the AOR.

Parent topic: Security for intercommunication