You can implement security in two ways. The service requester can
either provide the security or you can implement security in CICS.
About this task
You can implement security in the CICS Service Flow Runtime using
one of the following components:
Procedure
- Configure RACF® or another external security manager to handle
request messages. CICS Service Flow Runtime does
not require users to sign on before issuing requests for processing. However,
you can specify authentication using RACF to check that the user ID is authorized
to invoke a service flow.
- Configure the WebSphere MQ-CICS bridge to provide security for
service requesters that are WebSphere MQ-enabled applications.
The
WebSphere MQ-CICS bridge uses the AUTH parameter that
is passed to the CICS® bridge monitor task at startup to establish the
authentication level required for the CICS bridge link task.
- If you are using FEPI with PassTickets, set the AUTH parameter
to a value other than LOCAL.
- To establish different levels of authentication, initiate multiple
bridge monitor tasks with different AUTH parameters.
The WebSphere MQ-CICS bridge checks that the user has the authority
to run the CICS bridge link task, based on the user ID and password. The CICS Service Flow Runtime programs and processes
run under the user ID and password established for the CICS bridge link task.
See the WebSphere MQ for z/OS System Management Guide for information
on security while using WebSphere® MQ with CICS.