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

122 CICS Transaction Gateway V5
Verifying EPI signon capable security
In our scenario, we set USEDFLTUSER(YES) on our CONNECTION definition.
This means the CTIN and CESN requests will run using the default user ID.
Therefore we needed to supply only a valid user ID and password for the request
to run our actual EPI transaction.
Tip: If you set USEDFLTUSER(YES) on your CONNECTION definition, then
you should realize that this will allow any user to install EPI terminals in your
CICS region without any authentication, since any user ID and password
specified on the Terminal constructor will be ignored for the install of the
terminal by the CTIN transaction. If you wish to restrict this behavior, you
should specify USEDFLTUSER(NO) on the CICS CONNECTION definition
and then specify a valid user ID and password for the CTIN install. In
Figure 6-10 this is controlled by the termUserid and termPassword fields. If you
do this, you must also permit READ access to the CTIN transaction for the
desired user ID using the following commands:
RDEF TCICSTRN SCSCPJA4.CTIN UACC(NONE)
PERMIT SCSCPJA4.CTIN CLASS(TCICSTRN) ID(CICSRS2) ACCESS(READ)
SETROPTS RACLIST(TCICSTRN) REFRESH
In Example 6-7, you can see the results of a successful call to the EPIP
transaction from our SignonCapable EPI application.
Example 6-7 Successful test with SignonCapable EPI application
C:\itsoctgv5\Java>java itso.cics.epi.SignonCapable tcp:\\volga SC62PJA4 CICSRS2
PASSWORD
Gateway URL: tcp://volga/
Region: SC62PJA4
Userid: CICSRS2
Password: PASSWORD
Adding signon capable terminal with userid:null
Netname: CCLIE017
Starting CESN
Entering userid and password
DFHCE3549:Now signed on to CICS
Starting EPIP
EPIP results
Time : 02:12:01
Date : 25/06/02
Applid : SCSCPJA4
Userid : CICSRS2
Closing terminal and gateway