DB2 password after network password has changed

[b***@celink.com]

We are new to DB2 v9.1 and have a problem/question about when a user is required to change their windows network password and then they can no longer access DB2 tables through the ODBC driver (cli.ini). How can this be set up to automatically change the DB2 and CLI password to match the new network password, or is there some other way to allow the user to access DB2 without the network and DB2 passwords having to match.

thanks
Brent

[Knut Stolze]

Post by b***@celink.com
We are new to DB2 v9.1 and have a problem/question about when a user is
required to change their windows network password and then they can no
longer access DB2 tables through the ODBC driver (cli.ini). How can this
be set up to automatically change the DB2 and CLI password to match the
new network password, or is there some other way to allow the user to
access DB2 without the network and DB2 passwords having to match.

DB2 doesn't manage passwords. It uses security plug-ins for that. The
defaults a security plug-in that refers to the underlying operating system
for authentication. Thus, if everything is set up properly, a change of
the user's password in the underlying security product will be
automatically in effect for DB2 as well.

So what exactly is the error message that DB2 returns? Which platform do you
run DB2 on? What do you find in the output of the "db2diag" tool?

p.s: There is only a file "db2cli.ini", which contains the configuration of
the DB2 CLI driver. But you shouldn't edit that file manually and use the
DB2 command UPDATE CLI CFG instead.

[b***@celink.com]

Thanks Knut,

if we log into the network and change our password the CLI file is not updated with the new password. The only access the users have is through the DB2 ODBC driver. Any idea where the mis-match might be occuring so we could go back and get the users setup correctly?
the error message we are getting is: SQL30082N Security processing failed with reason "24" ("username and/or password invalid") SQLSTATE=08001

Thanks
Brent

[Knut Stolze]

Post by b***@celink.com
Thanks Knut,
if we log into the network and change our password the CLI file is not
updated with the new password.

Do you have the password in the db2cli.ini file (if this is the "CLI file"
you are referring to)? Why do you do that?

Post by b***@celink.com
The only access the users have is through
the DB2 ODBC driver. Any idea where the mis-match might be occuring so we
could go back and get the users setup correctly?
the error message we are getting is: SQL30082N Security processing failed
with reason "24" ("username and/or password invalid") SQLSTATE=08001

As I said: DB2 doesn't manage passwords. Your

Post by b***@celink.com
Thanks
Brent

[Knut Stolze]

Post by Knut Stolze

Post by b***@celink.com
Thanks Knut,
if we log into the network and change our password the CLI file is not
updated with the new password.

Do you have the password in the db2cli.ini file (if this is the "CLI file"
you are referring to)? Why do you do that?

Post by b***@celink.com
The only access the users have is through
the DB2 ODBC driver. Any idea where the mis-match might be occuring so
we could go back and get the users setup correctly?
the error message we are getting is: SQL30082N Security processing
failed with reason "24" ("username and/or password invalid")
SQLSTATE=08001

As I said: DB2 doesn't manage passwords. Your

... underlying security product/mechanism manages those. Therefore, if you
manage all users/passwords with that security mechanism (and solely with
that) and DB2 has a security plugin for that mechanism, you won't have a
problem with DB2. But as soon as you start managing passwords somewhere
else (e.g. some other config files), the whole thing falls apart.