I am setting up the stash backup client. It requires a stash user/password. We don't think it's a good idea to place someone's windows password in a plain text file, or pass it via command line. Also, our active directory password expires every 90 days, therefore the password will need to be reset in the properties file every 90 days. It is something that someone could easily forget.
Wondering how people have got around this problem ... ?
We create service accounts wich do not expire, but their password is not stored in cleartext anywhere.
Think about using a Stash internal account for backups, which also do not expire.
We don't have the password for the internal account. The person who created that account has left the company. Can another admin delete that user, and change their own profile to use the internal user?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any admin should be able to add internal accounts. There is not just one single internal account - you can create as many as you want (within licensing, of course) and grant them whatever level of access they require.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.