The local node and the remote z/OS node might not share the same user registry.
Two additional properties are available on the optimized
local adapters RAR connection factory to give the request an opportunity
to log on and to specify the user ID to use for the optimized local
adapters interaction:
- Username
- The user name to use when executing the optimized local adapters
interaction
- Password
- The password to use with the Username property.
When specifying Username and Password, a logon occurs
just before the optimized local adapters interaction is performed.
If the logon is successful, the z/OS user ID corresponding with the
Username is sent with the optimized local adapters request. Currently,
the z/OS user ID is used when
communicating with CICS® by
using the optimized local adapters link server.
For Versions
8.0.0.2 and earlier, the target CICS transaction
is started using the z/OS user
ID.
For Version 8.0.0.3 and later, the
target CICS transaction is started using the z/OS user ID only if
the link server is started with the SEC=YES parameter and the CICS
region is running with SEC=YES. For IMS, this user ID will be propagated
and asserted only when the SYNC-TO-THREAD option is enabled on the
WebSphere Application Server for z/OS server and the OTMASE=FULL OTMA
parameter is in effect.
A
J2C JAAS alias may also be used to provide the Username and Password
values. To use a J2C JAAS alias, in the administrative console, click Resources
> Resource Adapters > J2C connection factories > cf_name >
JAAS-J2C authentication data > alias_name,
and enter the userid and password. The resource adapter retrieves
the userid and password from this setting. Should a JAAS alias be
provided as well as the Username and Password on the connection factory,
the Username and Password on the connection factory will take precedence.
The setUserid() and setPassword() methods on the ConnectionSpecImpl
takes precedence over both of these other methods.