Resource and transaction security for application-generated responses

If you have obtained an authenticated user ID for a web client, which has a profile in your security manager, this user ID is applied to the alias transaction that is used for the application-generated response.

About this task

You either give appropriate permissions to the web client user IDs or you supply your own standard user ID as an override. Whether or not you decide to use web client user IDs for resource security checking, you must ensure that the user ID for the alias transaction has the appropriate permissions.

You define alias transactions by TRANSACTION resource definitions. The alias transaction for each application-generated response is specified by the URIMAP definition for the request or by an analyzer program. The default is the CICS-supplied alias transaction CWBA, which applies when either web-aware applications or COMMAREA applications are used to provide the response.

The user ID under which the alias transaction runs must have authority to perform these tasks:
  • Attach the alias transaction, if transaction-attach security is specified for the CICS region. Transaction-attach security is controlled by the system initialization parameter XTRAN. The default is YES (transaction-attach security is active).
  • Access any CICS® resources used by the alias transaction, if resource security is specified for the alias transaction. Resource security is controlled by the RESSEC attribute in the TRANSACTION resource definition for the alias transaction. The default is NO (no resource security), and NO is also the supplied setting for CWBA.
  • Access any CICS system programming commands used by the alias transaction, if command security is specified for the alias transaction. These system programming commands are used in the user-written application program that produces the response. Command security is controlled by the CMDSEC attribute in the TRANSACTION resource definition for the alias transaction. The default is NO (no command security), and NO is also the supplied setting for CWBA.
When a web client makes a request to CICS web support, and the response is provided by an application, CICS selects a user ID for the alias transaction in the following order of priority:
  1. A user ID that you set using an analyzer program. This user ID can override a user ID obtained from the Web client or supplied by a URIMAP definition.
  2. A user ID that you obtained from the Web client using basic authentication, or a user ID associated with a client certificate sent by the Web client. If authentication is required for the connection but the client does not provide an authenticated user ID, the request is rejected.
  3. A user ID that you specified in the URIMAP definition for the request.
  4. The CICS default user ID, if no other can be determined.
Depending on your CICS web support architecture, you might be using one or several of these types of user ID, for different requests. If you obtain an authenticated user ID for a web client, it is used for the alias transaction unless you take action to override it.

Take the following security actions for application-generated responses:

Procedure

  1. If you are obtaining authenticated user IDs for web clients, but you do not want to use these for security checking for your application-generated responses, you use an analyzer program to override web client user IDs with a standard user ID for the relevant alias transactions. (You can use the CICS default user ID.) Place the analyzer program in the processing paths for the requests where you want to supply this override. See Analyzer programs. Make sure that this user ID has a user profile defined in your security manager. When you have set up a standard user ID, you can give the required permissions, as described in the remaining steps of this procedure, to the standard user ID.
  2. If you are not obtaining authenticated user IDs for web clients, select suitable user IDs to be standard user IDs for your alias transactions. Unless you just want to use the CICS default user ID, specify your chosen user IDs in the URIMAP definitions for the requests, or set up an analyzer program to specify them. Make sure that the standard user IDs have user profiles defined in your security manager.
  3. Assuming that transaction-attach security is specified for the CICS region, ensure that all the possible user IDs for your alias transactions have authority to attach the transaction. All user IDs might include web client user IDs, if you are obtaining them and are not overriding them, or a standard user ID that you have specified in a URIMAP definition or analyzer program, or just the CICS default user ID. See Transaction security.
  4. Optional: Apply resource-level security checking for the resources used by an alias transaction:
    1. Identify all the CICS resources used by the alias transaction, and determine which of them are subject to resource security checking in your CICS region. Here are some resources that might be used by an application program for CICS web support and the system initialization parameters that control resource security checking for them:
      • CICS document templates (XDOC system initialization parameter)
      • Other application programs invoked by the main application program to perform business logic (XPPT system initialization parameter)
      • Temporary storage queues used to share application state across an HTTP request sequence (XTST system initialization parameter)
      • Files managed by CICS file control (XFCT system initialization parameter)

      Resource security checking for zFS files (XHFS system initialization parameter) does not apply when zFS files are used by an application program, because the files can be manipulated by an application program only when they are defined as CICS document templates, and CICS document template security controls access to them in this situation.

      If you are using an analyzer program, it is the main program for the alias transaction, and so is not subject to resource security checking (only to the transaction-attach security checking). However, note that the user-written web application program itself, and any converter program that you use, is subject to separate resource security checking. Similarly, if you are using a converter program but no analyzer program, the converter program is the main program for the alias transaction, but the application programs called by the converter program are subject to separate resource security checking.

    2. Give all the user IDs that are permitted to attach the alias transaction permission to use the secured resources used by the alias transaction.
    3. Specify RESSEC(YES) in the TRANSACTION resource definition for the transaction.
  5. Optional: To apply command security checking for any CICS system programming commands used by an alias transaction:
    1. Confirm that command security is active in the CICS region. Command security is activated by the XCMD system initialization parameter.
    2. Identify the CICS system programming commands used by the application program or programs, analyzer program (if used), and converter program (if used), that are associated with the transaction. CICS resources subject to command security checking has a checklist of commands.
    3. Give all the user IDs that are permitted to attach the alias transaction permission to use the commands used by the alias transaction.
    4. Specify CMDSEC(YES) in the TRANSACTION resource definition for the alias transaction.

What to do next

For any security checking to take place in a CICS region, set the SEC=YES system initialization parameter.


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