Changing connection to SSL

[pmb88]

I have Vault Standard 10.0.2. I am transitioning to use SSL TLS 1.2 and I found a post here, viewtopic.php?t=22873 , that mentions in the notes that the plugins may need to be updated. The post is several years old. Would that still hold true today?

[Tonya]

Hello,

There is still a separate download needed when TLS 1.2 is installed. You can access the client on our download page:

https://www.sourcegear.com/vault/downloads.html

Search for "Vault GUI Client update for TLS 1.1/1.2.".

Thanks,

Tonya

[pmb88]

It says I need to contact technical support for configurations. What configs will need to be made?

Also the vault url is stored in the Visual Studio solution file. Would I need to update it there as well?

[Tonya]

Recommended deployment for the procedure is to :

a) Check and verify .NET Framework 4.5 is installed on each client.
b) Have the latest Vault Standard Client installed.
c) Download the Vault Standard - "Vault GUI Client update for TLS 1.1/1.2". This is a compressed .zip file.
d) You can extract that into a new directory you create under "\Program Files (x86)"

OR

Some people have extracted it on TOP of the existing Vault 10 installation, and overwrote those existing files.

In either case, once extracted, you should be able to connect to your TLS 1.1/1.2 IIS Server using those Vault related binary files.

Thanks,

Tonya

[pmb88]

Tanya,

What does this one do, "Vault Command Line Client update for TLS 1.1/1.2"?

Just to clarify, if I extract it into a different directory, under "Program Files(x86)", the client will use the new binaries, regardless if it's in the SourceGear folder?

I would also have to tweak the solution files to use the secure url correct?

[Tonya]

Hello again,

The Vault Command Line Client update for TLS 1.1/1.2 is for Vault Command-line user's who need support for TLS 1.1/1.2.

Do you use Vault integrated with Visual Studio or only the Vault GUI client alone? The VS Enhanced Client on Vault 10 works with TLS 1.2.

Thanks,

Tonya

[pmb88]

Tanya,

Most of the time we use the VS Enhanced Client. However, we do use the standalone client occasionally.

[Tonya]

If you upgrade to TLS 1.1/1.2 only (disable SSL) then the designated clients to work in this environment are the only ones that will work. In regards to Visual Studio integration, Vault for Visual Studio Extension (VS 2017/2019) is the only one that will work with TLS 1.1/1.2.

Tonya

[pmb88]

I have Visual Studio 2015. I want to use this in SSL with TLS 1.1/1.2. SSL would not be disabled.

So, would the VS client work with this?

"Vault GUI Client update for TLS 1.1/1.2", would only apply to the standalone client, correct?

[Tonya]

TLS 1.1/1.2. is not supported in Visual Studio 2015.

Yes, the download you are referring to below "Vault GUI Client update for TLS 1.1/1.2" only applies to the stand-alone Vault GUI Client.

Tonya

[pmb88]

Tonya,

Before I make the switch, I want to make sure I am understanding your points correctly.

In order for me to run this on my Visual Studio version, I would have to:

• Cease using the client in Visual Studio and set the source control option to 'None' in options.
• Begin using the standalone client for everything.
• Download and install the update to the standalone client you mentioned above.

You've mentioned that the update does not need to be extracted into the SourceGear folder, as long as it's extracted somewhere in 'Program Files (x86)', correct?

There's nothing on the server I would have to do besides adding the certificate, correct?

Also, the connection string to the repository is written in the solution file. I have a couple of questions on that:

• Will that still write the connection string if I add VS projects through the standalone client?
• Will it try to connect in Visual Studio, if I disable the Enhanced Client? I would presume that would not happen

[Tonya]

If you can't upgrade to Visual Studio 2017/2019 and need to use TLS 1.1/1.2 then you will need to use the Vault GUI Client only (and can no longer use the Vault integration within VS). The steps you have listed below are correct.

In regards to your connection concerns, you will need to unbind the solution, save it and then check it back in using the Vault GUI Client. I have copied below a link that will provide you with more details:

viewtopic.php?f=13&t=18956&p=70077#p70077

Please keep in mind this will remove the bindings for everyone. So if you have other Vault user's who are utilizing VS 2017/2019 and plan to continue using integration, this option will not work.

Tonya

[pmb88]

There's no future plans to update Vault or the Extension to make it work in 2015 in 1.1/1.2, correct?

[Tonya]

Yes, you are correct.

Tonya