-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Open Repository from Azure DevOps #385
Comments
@lszomoru @joyceerhl This issue has progressed - not quite to a happy conclusion, In testing with our vendors, we learned that on our new SASE solution we are doing https decryption and inspection on more internet URLs including where we previously we were not - due to our company threat protection policy and application of security vendor best practices. To make VS Code Remote Repository to Azure DevOps work, we applied a very large number of exceptions to https decryption, based on this Microsoft page: https://learn.microsoft.com/en-us/azure/devops/organizations/security/allow-list-ip-url?view=azure-devops&tabs=IP-V4 We have not narrowed it down any further as yet. *** Typically issues like this are TLS certificate trust - where our internally trusted certificate is not trusted. Anyway where there is an issue, the client (normally a browser) will report the issue and we can resolve it. However in this case the client is VS Code extension, and the extension does not report an issue - it just silently fails. We currently don't actually know a precise fix for it, just a shotgun of exceptions that is not ideal. Https decryption and inspection is a critical plank of our security infrastructure. Can the VS Code and/or extension logging and/or error presentation to the user be improved? |
@mikew3432, could you check the "Azure Repos" output channel to see if there are any errors there? |
Thank you @lszomoru! that is very helpful. We can use this info. Actually I didn't know about the Output panels. Much appreciated. |
Glad the information is helpful. Please keep me posted on whether things will work out. |
|
Hello dear reader - this is a networking-caused issue but hard to fathom and hoping for assistance. It is probably an error handling bug?
I go to Open Remote Repository and Open Repository from Azure Repos, the Azure Active Directory Tenant picker is not displayed - and goes straight to an empty Azure DevOps Organization picker.
The catch is - this only happens connected on our new VPN. The problem is, how to determine what is broken. The network appliance logs are (too) abundantly full of successful connections... The root cause is undoubtedly some network/security policy, it works fine on our old VPN. However I'm finding it hard to troubleshoot and the network flow is not documented afaik.
Issue in pictures:
<-- normally at this point in the sequence, I would get shown a couple of AAD tenant IDs, however it skips it -->
^^^ Unable to open a Azure DevOps repo.
The text was updated successfully, but these errors were encountered: