how to maitain the authentication details/passwords in a 50 people company

Posted by sabya on Server Fault See other posts from Server Fault or by sabya
Published on 2009-10-27T15:19:19Z Indexed on 2010/04/08 10:33 UTC
Read the original article Hit count: 382

Filed under:
|
|

What is the process that you guys follow to maintain authentication details like login ids and passwords? There will be definitely some shared passwords. So, the target is to minimize the impact when someone is leaving the company.

By "shared password", I mean, the account, which is shared among multiple people in the company.

The issues that the process should address are: -

  1. Affected areas. Quickly find the resources to which the leaving user was having access to.

  2. Forgetting password. What happens if a user forgets an authentication details? How does he get it? I think he shouldn't ask a team mate. I mean no-verbal communication.

  3. Find dependencies of a resource. Suppose I am changing the password for a mail account, which is getting used by some automated scripts to send mails. Here, the scripts are dependent on the mail account, so changing the password of the mail account means we have to change the password in the script too. So, how do find all the dependencies of a resource?

I'd prefer a process which addresses these issues. But you can also recommend products which are open source and not hosted. I have gone through PassPack, but they don't solve #4.

There is a similar question here. But that does not exactly answer my question.

© Server Fault or respective owner

Related posts about passwords

Related posts about process