When logging into our Git solution, Atlassian BitBucket Server, our IT department has configured credentials so that our Windows logins are the same as our BitBucket Server logins. So when Windows passwords change--mandated by our IT department every 90 days, the passwords are also changed for BitBucket Server as well as many other programs we use at our company. DbForge for SQL Server uses HTTP to login and must be changed manually, as far as I know.
Is there a way to insert a Windows Authentication certificate to automatically update credentials? This would save tremendous time for my data reporting department having to relink 16 databases every 90 days.
Login Credentialing Issues with Windows Automatic Authentication
Re: Login Credentialing Issues with Windows Automatic Authentication
Unfortunately, we won't be able to implement this possibility soon since we don't know how the BitBucket server is configured, however we will investigate it.
In the closest product builds, we will add a possibility to change the password of the existing link with no need to relink. Before it's done, it can be workarounded as follows:
1. Open the following file (for example, with dbForge or Notepad):
2. Find the following tags in the file:
3. Backup the existing password for future use.
4. Open the linking wizard.
5. Select the Source Control Repository with the name specified in the tag:
6. Change the password, click 'OK' and close the wizard.
7. Reload the open vc.xml file in order the changes to take effect.
8. In the tag a new encrypted password will display. Backup the password for future use as well.
9. Open the following file (for example, with dbForge or Notepad):
10. Replace all entries of the old password to the new one.
11. Save the changes.
12. Restart dbForge.
In the closest product builds, we will add a possibility to change the password of the existing link with no need to relink. Before it's done, it can be workarounded as follows:
1. Open the following file (for example, with dbForge or Notepad):
Code: Select all
AppData\Devart\dbForge Studio for SQL Server\vc.xml
Code: Select all
<Repository xsi:type="GitRepositoryInfoSerializationModel">
<Name>repository_name</Name>
...
<HttpAuthenticationInfo>
...
<Password>encrypted_password</Password>
<Password>encrypted_password</Password>
4. Open the linking wizard.
5. Select the Source Control Repository with the name specified in the tag:
Code: Select all
<Name>repository_name</Name>
7. Reload the open vc.xml file in order the changes to take effect.
8. In the tag
Code: Select all
<Password>encrypted_password</Password>
9. Open the following file (for example, with dbForge or Notepad):
Code: Select all
AppData\Devart\dbForge Studio for SQL Server\SourceControl\sclinks.xml
11. Save the changes.
12. Restart dbForge.
Re: Login Credentialing Issues with Windows Automatic Authentication
I did not find this path on my PC. I followed the path that did have Devart\dBForge Studio for SQL Server and there was no vc.xml file. I searched the entire hard drive of both my Windows 7 Pro laptop and my Windows 7 Pro virtual machine and neither PC had a file anywhere on the hard drive with the name vc.xml. Please advise.
Re: Login Credentialing Issues with Windows Automatic Authentication
The path was for dbForge Studio for SQL Server. In case you are using dbForge Source Control for SQL Server, please use the following path:
Code: Select all
%appdata%\Devart\dbForge Source Control for SQL Server\vc.xml
Re: Login Credentialing Issues with Windows Automatic Authentication
I am using Enterprise DB Forge for SQL Server. I do not have a file called vc.xml following any path on my laptop or my VM. Please advise.
Re: Login Credentialing Issues with Windows Automatic Authentication
Could you please provide us a screenshot of the content of the folder from the PC with the existing links:
You can reply straight to our support system at supportATdevartDOTcom
Code: Select all
%appdata%\Devart\dbForge Studio for SQL Server\