Login fails when connecting to TFS instance with self-signed certificate
See original GitHub issueAttempting to login against our local TFS instance which uses a cert signed by an internal/private CA fails. Adding the --debug
switch confirms my suspicion that the cert isn’t trusted. Is there any way to provide an alternate CA bundle? Or to tell the CLI to accept a specific CA or cert?
urllib3.connectionpool : Retrying (Retry(total=2, connect=3, read=3, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:748)'),)': /tfs/defaultcollection2/_apis
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
SDK prompting Error: self signed certificate in certificate chain
This extension works successfully in many TFS / Azure DevOps servers. However, we are getting error “self signed certificate in certificate chain” in...
Read more >Error: SSL certificate problem: unable to get local issuer ...
If you are using self-signed certificate, you may not be able to connect to TFS from the plugin. Error message: Caused by: javax.net.ssl....
Read more >TFS Build Agent Fails to Configure & Run with TFS2018 Self ...
The self-signed certificate isn't trusted. Log in to your build machine as your build agent user account and then run 03-import-iis-self-signed ...
Read more >Setting up a TFS demo environment with SSL | by Grazi Bonizi
Access the Team Foundation Server Administration Console, click on Application Tier, then in Change Public URL. Type the HTTPS URL and click on ......
Read more >How to avoid the Team Foundation server certificate issue
If you are using the Team Foundation server configured over SSL and experiencing the error below: com.microsoft.tfs.core.exceptions.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s exactly what I was looking for, and it works great. Thanks for the follow up.
@markjgardner There is a safer way to workaround this issue. You can take your servers certificate, and copy it to a Base-64 encoded X.509 file (In windows you would open the certificate, go to details tab, and choose ‘copy to file…’ button). Then you can set the following environment variable
REQUESTS_CA_BUNDLE
to the file path of your cert file. Once this is done you will no longer get verification errors. Can you give this a try?