Skip to main content

Azure DevOps Server–Switch from HTTP to HTTPS–Part 2

With the release of Azure DevOps Server 2022, I thought it would be a good time to finally make the switch to HTTPS for our internal Azure DevOps server. With the idea to minimize downtime, I decided to first introduce the HTTPS endpoint before upgrading the Azure DevOps server. But o boy, what I thought would be an easy task turned out to be quite a journey.

Yesterday I explained the actions required on the server side, today we move on to the client side.

Visual Studio TFVC workspaces

In Visual Studio, we have to update our connections in Team Explorer.

  • Therefore click on the green Connect icon in Team Explorer.

  • Click on Manage Connections and Connect to a project…

  • Right click on the existing connection and choose Remove from the context menu.

  • Click on Add TFS server, enter the updated Server URL and click on Add.

  • Restart your Visual Studio instance.

After doing these steps, I noticed that still the original URL was shown when I reopened a project in Visual Studio:

There is one last step you need to take for your TFVC workspaces:

Remark: You need to repeat this command for every Visual Studio version you have installed on your dev machine.

GIT repositories

For our Git repositories, we need to update our remote origin. We can do this through the command line:

git remote set-url origin <remote-url>

You can verify that the remote’s URL was successfully changed by listing the remote connections:

git remote -v

You can also update the remote origin through Visual Studio:

  • From the Git menu, choose Manage Remotes.

  • Select the remote origin and click on Edit.

  • Update both URL’s and click on Save.

Important:

By default, projects that use Git for version control will fail to validate the SSL certificate you have configured for Azure DevOps Server.

This is because unlike Azure DevOps Server and Visual Studio, Git does not recognize the Windows certificate store. Instead, it uses OpenSSL for its certificate store. A solution is to register your certificate in OpenSSL, luckily an easier solution is available since Git for Windows 2.14. You can configure Git to use SChannel, the built-in Windows networking layer. This means that it will use the Windows certificate storage mechanism and you do not need to explicitly configure the curl CA storage mechanism.

Therefore execute the following command:

git config --global http.sslbackend schannel

More information:

Labels:

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B
Read more

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more