01.01.2013 Views

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Surrogate user security<br />

<strong>CICS</strong> performs surrogate user security checking in a number of instances to<br />

ensure that the authenticated user is authorized to act for another user. It can<br />

also be used by the <strong>CICS</strong> TG itself to ensure that the started task user ID is<br />

authorized to initiate work on behalf of the user ID flowed in an ECI request.<br />

Intercommunication security<br />

Intercommunication security in <strong>CICS</strong> is concerned with incoming requests for<br />

access to <strong>CICS</strong> resources. Requests from the <strong>CICS</strong> TG can arrive via APPC<br />

(ISC) or EXCI (MRO) connections and the two are treated somewhat differently.<br />

<strong>The</strong>re are three fundamentally different intercommunication security checks that<br />

can be performed as follows:<br />

► Bind security<br />

This verifies the system wishing to connect (bind) to <strong>CICS</strong> is authorized to do<br />

so.<br />

► User security (or in LU 6.2 terms, conversation level security)<br />

This causes a check to be made against the flowed user ID when an inbound<br />

requests attaches the requested transaction in <strong>CICS</strong>. This behavior is defined<br />

in the ATTACHSEC parameter on the CONNECTION definition. For MRO or<br />

EXCI requests from the <strong>CICS</strong> TG, this should always be IDENTIFY, meaning<br />

that only the user ID is checked. For APPC (or TCP62) connections from the<br />

<strong>CICS</strong> TG, this should be set to VERIFY, meaning both the user ID and<br />

password are checked. For ECI over TCP/IP connection from the <strong>CICS</strong> TG,<br />

this should be set in the TCPIPSERVICE to VERIFY.<br />

► Link security<br />

This is an additional level of authorization checking that can apply to the<br />

attached transaction. A specific user ID (the link user) is defined on the<br />

connection with the remote system. This user ID must be authorized to have<br />

access to all transactions and resources invoked through this connection.<br />

This concept applies equally to MRO and ISC.<br />

We discuss how each of these apply to security with <strong>CICS</strong> TG in this chapter.<br />

6.2 <strong>CICS</strong> TG security scenarios<br />

In the following sections, we present three security scenarios, as follows:<br />

► An ECI call to a <strong>CICS</strong> program using the <strong>CICS</strong> TG for z/OS and an EXCI<br />

connection to <strong>CICS</strong> (see 6.2.1, “ECI to <strong>CICS</strong> TG for z/OS (EXCI)” on<br />

page 102)<br />

Chapter 6. <strong>CICS</strong> TG security scenarios 101

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!