Database access change after upgrading to Vault 4.1.2
Moderator: SourceGear
-
- Posts: 33
- Joined: Fri May 12, 2006 8:36 am
Database access change after upgrading to Vault 4.1.2
We upgraded to Vault 4.1.2 and now the login 'NT AUTHORITY\NETWORK SERVICE' has permission in our database instead of the user sgvaultuser. Now that the installation has been completed, how can I configure Vault to use the credentials for the user sgvaultuser instead of 'NT AUTHORITY\NETWORK SERVICE'?
Re: Database access change after upgrading to Vault 4.1.2
It might be easiest just to uninstall Vault, then reinstall, taking care to use SQL Server authentication during the SQL Server setup portion of the installation. This will create the sgvaultuser account.
The other option would be to manually create the sgvaultuser, giving it the same password as the Vault admin. Then, in the Vault web.config file in the Vault Service directory, change the authentication method (near the bottom of the file) by commenting out Windows authentication, and using SQL Server authentication instead. The encrypted password in the Vault Web.config file will be the Vault Admin password, which we also use for sgvaultuser.
The other option would be to manually create the sgvaultuser, giving it the same password as the Vault admin. Then, in the Vault web.config file in the Vault Service directory, change the authentication method (near the bottom of the file) by commenting out Windows authentication, and using SQL Server authentication instead. The encrypted password in the Vault Web.config file will be the Vault Admin password, which we also use for sgvaultuser.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 33
- Joined: Fri May 12, 2006 8:36 am
Re: Database access change after upgrading to Vault 4.1.2
Linda,
Thanks for the response. I can create the user manually no problem. But can you outline the specific web.config entries I will need to add and copy from?
Thanks for the response. I can create the user manually no problem. But can you outline the specific web.config entries I will need to add and copy from?
Re: Database access change after upgrading to Vault 4.1.2
This is what the Vault Service web.config should have in its connection strings if you're using SQL Server authentication. Note that Windows mode is commented out:
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='true'; Server=(local); Database=sgvault; User ID=sgvaultuser; pwd=FQgy21q1sp0=" />
<!-- INTEGRATEDWINDOWSMODE-add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='true'; Server=(local); Database=sgvault; Integrated Security='true'" />INTEGRATEDWINDOWSMODE- -->
</appSettings>
If sgvaultuser doesn't have the same password as the Vault Admin, you can modify this section, changing pwd to password, ie: User ID=sgvaultuser; password=newpassword.
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='true'; Server=(local); Database=sgvault; User ID=sgvaultuser; pwd=FQgy21q1sp0=" />
<!-- INTEGRATEDWINDOWSMODE-add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='true'; Server=(local); Database=sgvault; Integrated Security='true'" />INTEGRATEDWINDOWSMODE- -->
</appSettings>
If sgvaultuser doesn't have the same password as the Vault Admin, you can modify this section, changing pwd to password, ie: User ID=sgvaultuser; password=newpassword.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager