| Author |
Message
|
| Christy Kestler |
 Posted: Wed Feb 12, 2003 10:12 am Post subject: CICS to IMS Bridge Authentication Options? |
 |
|
Newbie
Joined: 12 Feb 2003
Posts: 4
|
| Would like to know about options to disable authentication when using IMS Bridge. Will need authentication for most applications. Only want to establish trusting with CICS applications that put messages to IMS Bridge in order to trigger IMS transactions. |
|
| Back to top |
|
 |
| LuisFer |
| Posted: Thu Feb 13, 2003 10:29 am Post subject: Re: CICS to IMS Bridge Authentication Options? |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
In order to exec IMS tx tx by the brigde (OTMA client) need's to receive an user & correct passwd. You can do a Racf User authorized for a few codes of IMS Tx. Also you can disabled the IMS security  .
1.- Associate a Racf User to the Address Space of the QMGR.
2.- Authorize this user to EXEC the Tx you need. |
|
| Back to top |
|
|
| Christy Kestler |
| Posted: Thu Feb 13, 2003 10:44 am Post subject: |
|
|
Newbie
Joined: 12 Feb 2003
Posts: 4
|
Although we can enable the authorization by passing a password or passticket, to OTMA, we would like to avoid this 2nd authorization check ONLY when a CICS transaction is sending a message to the IMS Bridge. The users for these transactions would have already been authorized on our system, and we would prefer not to pass the password or use a passticket.
We need to have OTMA continue to validate id and password through RACF for non-CICS transactions that send messages to the IMS Bridge.
OTMA also needs to continue to validate authorizations for IMS CONNECT, so we can't turn it off.
Any other suggestions? We appreciate all advice! |
|
| Back to top |
|
|
| LuisFer |
| Posted: Thu Feb 13, 2003 10:53 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
Do you need protected passw?
The CICS is on the same ZOS image or in the SYSPLEX? |
|
| Back to top |
|
|
| LuisFer |
| Posted: Thu Feb 13, 2003 10:59 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| The IMS CONNECT can not validate the user/passw (it's a security Hole of the IMS CONNECT) if an habilidous programmer decides not to do it.... |
|
| Back to top |
|
|
|
|
