Security considerations

When an API program requests a connection to CICSPlex SM, the CMAS being connected to attempts to extract user authorization data from the environment. How the connection is established depends upon whether such authorization data exists and whether security is active in the CMAS.

If security exists
Regardless of whether CMAS security is active, if a security environment exists where the API program is running:
  • The API security routine, EYU9XESV, is not called.
  • The USER and SIGNONPARM options on the CONNECT command are ignored.
  • The API program is connected with the user ID of the invoking user, as obtained from the accessor environment element (ACEE).
Note: If CMAS security is not active, the ACEE user ID is not validated by CICSPlex SM.

This type of security environment may exist when a program runs under TSO, batch, NetView®, or a local MAS where CICS security is active. Security checking is performed by the environment where the API program is running.

If security does not exist and CMAS security is not active
  • The API security routine, EYU9XESV, is not called.
  • The USER and SIGNONPARM options on the CONNECT command are ignored.
  • No sign-on is performed. However, the user ID specified in the XESV_CONN_USERID field of the security routine parameter block, EYUBXESV, is associated with the connection.
This type of security environment may exist when a program runs under a local MAS where CICS security is not active. Since CMAS security is not active, no security checking is performed.
If security does not exist and CMAS security is active
  • The API security routine, EYU9XESV, is called.
  • The USER and SIGNONPARM values from the CONNECT command are passed to EYU9XESV.
  • A sign-on is performed using the user ID returned by EYU9XESV, but no password checking is performed. By default, EYU9XESV returns the default CICS user ID for the CMAS (the DFLT_UID value).
This type of security environment might exist when a program runs under a local MAS where CICS security is not active. Since CMAS security is active, security checking is performed by EYU9XESV.
Table 1 summarizes the levels of API security and the conditions under which they are implemented.
Table 1. Possible API security environments
Environment Security CMAS Security No CMAS Security
YES EYU9XESV not called.

CONNECT options ignored.

User ID=ACEE.

EYU9XESV not called.

CONNECT options ignored.

User ID=ACEE (not checked).

NO EYU9XESV called.

CONNECT options passed.

User ID=As returned by EYU9XESV (sign-on with no password checking).

EYU9XESV not called.

CONNECT options ignored.

User ID= XESV_CONN_USERID (no sign-on).

For a description of the USER and SIGNONPARM options, see the API CONNECT command. See CONNECT command. For a description of EYU9XESV and information on customizing this security routine, see Securing.



eyup1af.html | Timestamp icon Last updated: Sunday, 4 June 2017