Take the tour ×

I was looking for solution everywhere, but maybe because lack of specialized words I can't find it.

I've got a problem in finding a program, but I don't know how to describe it in one word so I'll describe it in full way:

In company there is a usual situation when some of workers need to know login/password for external cooperants(for example suppliers, banks). For these company has only one login/password (because it identify company, not their workers). However there is a problem when worker is fired. He/She knows the password so there is a danger that he/she can make damage. So I'm looking for program that will store all company passwords, and only grant workers privledge to access site with login/password but without showing them.

I know that it is already similar topic here but as far as I understand, it is more like managing password inside company.

Thanks in advance for any help!

share|improve this question
One issue that neither of the answers (so far) have covered is the idea that a user might now he/she is about to be terminated, and write down the passwords from the password manager vault. So even if you find the perfect technical solution for password storage, you still need to change every password they have access to anyway. –  Polynomial Jan 11 at 10:44
add comment

4 Answers

firstly, it is bad policy to have non-individual based passwords and the first course of action would be to setup individual accounts for the users.

If the supplier cannot do that - then an alternative action would be to setup a simple federated trust model where the users never sign in to the 3rd party site but simply "single sign on" to the site using a federated trust model. There are industry standards for this such as SAML2 that allow you (and your company) to retain the identity management (including joiners/leavers/movers).

Clearly this will only work if you disallow normal login to the third party site. My client does this with every SaaS site that their employees use.

google for: Federation, SAML2, federated Single Sign On.

share|improve this answer
add comment

The usual practice is two-fold:

  • Restrict the number of shared passwords to the absolute minimum that is possible.
  • When an employee is terminated, change and shared password they knew.

The solution you are looking for - some sort of browser extension that stores the encrypted passwords for shared sites and then, on the user authenticating, uses the shared password to log on - would be great for your situation, but it has the problem that the end user is trusted (in the technical sense of the word, which is having to trust them since they have physical access to the computer).

share|improve this answer
add comment

I have to agree with Callum - the non-personal accounts are bad practice.

If you really can't change something about it - or it might take time to get there - have a look at:


one feature of it:

"Easily share and deploy credentials securely Using Dual Master Password functionality, users will have abilty to use credentials without knowing your organization's secure passwords"

...and no, I have no financial interest in this ;)

share|improve this answer
add comment

If I am not mistaken Secret Server is a product that lets you use rolebased access and hide the actual password as well unless you have the right to see it. You can still USE the password since clients for RDP, Putty and Web is integrated. That way the user can USE the password but dont see the password. Makes it easier, since you wont have to change every single password everytime someone is quitting their job. Copied from the User Guide for Secret server:

Secret Server's Launcher opens a connection to the remote computer or logs into a website using the Secret's credentials directly from the Web page. While this provides a convenient method of opening RDP and PUTTY connections, it also circumvents Users being required to know their passwords. A User can still gain access to a needed machine, but is not required to view or copy the password out of Secret Server. The Web Launcher will automatically log into websites using the client’s browser.

share|improve this answer
add comment

Your Answer


