Auto Login to Vault

[maggieo]

Hi there - we have recently installed our Vault Standard that we purchased.. The immediate need is to be able to have our users "auto-login" to Vault. We set it up with Windows Authentication specifically for this purpose and we are using AD groups for permissions/security. I see some old references to this in the forums, but nothing concrete.. One mentions an XML file, but I can't find that file on my machine. Another points out a registry key which I have but I don't know what to update in order for it to get my AD password.

Thanks, in advance, for your help with this.

- Maggie

[lbauer]

Users need a username and password to log into Vault. Using AD authentication means the user logs in with their network name and password. Passwords are managed by AD rather than Vault.

For auto login, users can set up profiles and configure Vault to automatically connect with that profile when the Vault GUI Client or Visual Studio is launched.

The Vault Web Client has "remember me" checkbox on login.

How are users connecting to Vault Server? Let me know and I can provide details on how to set up Profiles.

[maggieo]

Hi Linda - thank you.. I didn't get an email alert re your response - I'll fix that!
So - we installed the VaultServer_5_1_2_19281.msi on our server, and the VaultClient_5_1_2_19281.msi on the client pc's.

I don't think we're really using this via the "web" although IIS is turned on. I hope this helps and that we can use the "profile" method - or something.

Thanks much - Maggie

[lbauer]

To create the profile click Edit Profiles in the Connect to Server dialog.

Create the profile, then in the Connect to Server dialog, check "Automatically connect using this profile."

Create profile

Profile1.jpg (61.23 KiB) Viewed 7115 times

Automatically connect using profile

ProfileAutoconnect.jpg (34.76 KiB) Viewed 7115 times

[maggieo]

Thanks Linda - this works fine.. but what happens when our "Active Directory" password changes? Will we have to come in here each time and set it? I wonder if it will lock out accounts if it tries to connect with the old password before it's changed.. What I really hope is that there's a way not to have to go into here and change it.. Would we be better to set it up "NOT" using AD? Just have logins that never expire? In SourceSafe we just have logins with no passwords and it just always reconnects us. Hopefully there's something we can do here..

Also, on a different subject.. I know we asked if this could convert easily to SLQ 2008, but I forget if I asked about SQL 2012.. Can this convert easily to SQL 2012? We are going to skip over SQL 2008.. Right now it's on SQL 2000.

Thanks much - Maggie

[maggieo]

Hi therer - if we change and use SQL Authentication instead of Windows auth - can we use an AD group that gives rights to the SQL DB? The group already exists (Developers) and it has SYSADMIN rights to the server that Vault is installed on.. If we did that - then hopefully we would never have to change our passwords with regard to Vault.. Let me know - we are hoping to switch over this week - but there are several variables involved - and this is one of them!

Thanks much - Maggie

[lbauer]

what happens when our "Active Directory" password changes? Will we have to come in here each time and set it? I wonder if it will lock out accounts if it tries to connect with the old password before it's changed.. What I really hope is that there's a way not to have to go into here and change it.. Would we be better to set it up "NOT" using AD? Just have logins that never expire? In SourceSafe we just have logins with no passwords and it just always reconnects us. Hopefully there's something we can do here..

Also, on a different subject.. I know we asked if this could convert easily to SLQ 2008, but I forget if I asked about SQL 2012.. Can this convert easily to SQL 2012? We are going to skip over SQL 2008.. Right now it's on SQL 2000.

If the AD password changes, then the profile would need to change. If a user connected with an expired password, it would give them an error message. If they used the correct password, they would not be locked out.

You could use Vault authentication, and never change the Vault password.

Re: SQL 2012

We just did some prelimary testing using SQL Server 2012. It seems to work OK with Vault 5.x, but we're not ready to say it's fully supported there may be some issues we haven't uncovered yet. Vault 6.0 will have full support for SQL Server 2012.

[lbauer]

if we change and use SQL Authentication instead of Windows auth - can we use an AD group that gives rights to the SQL DB? The group already exists (Developers) and it has SYSADMIN rights to the server that Vault is installed on.. If we did that - then hopefully we would never have to change our passwords with regard to Vault.. Let me know - we are hoping to switch over this week - but there are several variables involved - and this is one of them!

The SQL auth vs Windows auth does not apply to Vault users. Vault users do not connect directly to the Vault database. Users connect to the Vault server, which does connect to the SQL Server database. The Vault server can be configured to use Windows auth or SQL Server authentication to log into SQL Server.