Our TFS is operated using HTTPS. How do I configure Timetracker for that?
TFS Timetracker supports HTTPS.
In this article, we will detail a scenario in which you encounter a problem setting up HTTPS protocol for your Team Foundation Server.
If you are using a self-signed SSL certificate, your browser will most likely send you a warning, and you will then need to add a security exception for this address.
In this situation, Visual Studio (and TFS Timetracker) will not connect to TFS hosted there and will display the following message:
TF31002: Unable to connect to this Team Foundation Server: https://machinename:443/tfs.
Possible reasons for failure include:
- The name, port number, or protocol for the Team Foundation Server is incorrect.
- The Team Foundation Server is offline.
- The password has expired or is incorrect.
Technical information (for administrator):
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
To solve this problem, you need to say to your OS that this connection is trusted. To do this, follow these steps:
- Export your certificate into the file with extension ".pfx" from IIS where Team Foundation Server is hosted.
- Copy this certificate to your machine, right-click it and then click "Install PFX" (and to all machines which connect to Team Foundation Server).
- On the first step of the wizard, select Store Location (we recommend that you choose Local Machine).
- Under "Certificate Store", select he "Place all certificates in the following store" radio button, click Browse, and then select "Trusted Root Certification Authorities".
- After completing the wizard, restart Visual Studio and TFS Timetracker.
Now TFS Timetracker and Visual Studio will connect to Team Foundation Server without error.