CDB Trusted Context and Already Authenticated

Jorg Lueke

CDB Trusted Context and Already Authenticated
If anyone has any experience with the Communications Database in going from
z/os to LUW your feedback will be appreciated! We have verified that we can
connect between our different systems, well not Oracle at this point. A key
requirement is that users can use the link for both scheduled and adhoc work
(the data serves mainly BI). We definitely don't want to start populating
USERNAMES table with 300 analysts for 12 or more servers. What they would
really like is to pass the userid/pwd in a parm (via somethign like a SAS
command) to the other side but I don't see any way you can pass along a
userid/pwd without specifying it in the CDB. That leaves the options
trusted on the link or already verified as a security option. The trusted
context again seems to be user based so it wouldn't work with 300 some
users. Already verified is easiest on our end, and I imagine on the LUW
side they just need to enable client authentication. But can you have both
types of connections come into the server?

_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/db2-content/index.html has THOUSANDS of free technical presentations!
DB2 LUW, DB2 z/OS, Performance, Installation, Tuning, Coding, BI, Warehouses, - among
many more categories of help waiting for you!
Whether you are an old hand or a DB2 newbie, we have presentations for every level.
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L