Re: change user password for huge amount of application server

Why not use Kerberos [1] as your database authentication mechanism?
Once you change your principal's password in the Kerberos realm, then
all of your systems will be up to date. No more pushing. But you'll
have to manage the wallets and pay for the Advanced Security Option.

You also have Kerberos in Oracle Database Enterprise User Security [2].

HTH,

DA+

[1] 
http://download.oracle.com/docs/cd/E11882_01/network.112/e10746/asointro.htm#i1007889
[2] 
http://download.oracle.com/docs/cd/E11882_01/network.112/e10744/configur.htm#DBIMI123

> Hi:
> We want to implement a db password change mechanism. We have a lot of
> application servers which have configuration file on local server.
>
> So if we change the password in configuration file, we need to push the new
> file to all of the application servers and it takes some time for the
> pushing. Some application servers can't login database using the old
> password during the pushing.
>
> The current workaround we can think of is to have two passwords in the
> configuration file, so the application server can try another one if the
> first one is failed.
>
> Do you have any better solution for this? Does oracle have any solution
> (ASO?) for this?
>
> Thank you in advance.
>
> --
> Eagle Fan
--
http://www.freelists.org/webpage/oracle-l


Other related posts: