Oracle passwords - how do you handle this?
From: <kaz_at_sis.bms.com>
Date: Thu, 14 Oct 1993 19:28:23 GMT
Message-ID: <1993Oct14.192823.8308_at_synapse.bms.com>
Joe Kazimierczyk
kaz_at_bms.com Received on Thu Oct 14 1993 - 20:28:23 CET
Date: Thu, 14 Oct 1993 19:28:23 GMT
Message-ID: <1993Oct14.192823.8308_at_synapse.bms.com>
At our site, we have about 12 different instances of Oracle (with more on the way). One thing that is becomming more of a problem is the number of separate Oracle accounts that some users need, and maintaining the passwords for these accounts. Since Oracle itsself doesn't have any method of password expiration, some of our inhouse applications now implement a method of doing this, and forcing the user to reset their password after x number of days. The problem here is that if someone changes their password as required by application A, they don't really know that this is the same account/password for applications C and D, but that applications E and F still use thier old password because it's in a different instance.
Joe Kazimierczyk
kaz_at_bms.com Received on Thu Oct 14 1993 - 20:28:23 CET