Get AuthenticationInfo failed exception

Rider IDE info:

JetBrains Rider 2018.2 EAP
Build #RD-182.3894.140, built on July 26, 2018
Rider EAP User
Expiration date: August 25, 2018
JRE: 1.8.0_152-release-1226-b7 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

Plugin Info:

Version: 1.125.0

Exception:

getAuthenticationInfoAsync failed

com.microsoft.alm.plugin.exceptions.TeamServicesException: KEY_VSO_AUTH_FAILED
	at com.microsoft.alm.plugin.authentication.facades.VsoAuthInfoProvider.getAuthenticationInfoAsync(VsoAuthInfoProvider.java:98)
	at com.microsoft.alm.plugin.authentication.VsoAuthenticationProvider.authenticateAsync(VsoAuthenticationProvider.java:69)
	at com.microsoft.alm.plugin.authentication.AuthHelper.getAuthenticationInfoSynchronously(AuthHelper.java:59)
	at com.microsoft.alm.plugin.context.ServerContextManager.getAuthenticationInfo(ServerContextManager.java:489)
	at com.microsoft.alm.plugin.context.ServerContextManager.createContextFromGitRemoteUrl(ServerContextManager.java:372)
	at com.microsoft.alm.plugin.context.ServerContextManager.createContextFromGitRemoteUrl(ServerContextManager.java:353)
	at com.microsoft.alm.plugin.context.ServerContextManager.getAuthenticatedContext(ServerContextManager.java:333)
	at com.microsoft.alm.plugin.context.ServerContextManager.getUpdatedContext(ServerContextManager.java:563)
	at com.microsoft.alm.plugin.operations.Operation$1.run(Operation.java:184)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Explain

When I’ve tried to login in my TFS account I enter the correct information ( email && password ). also i receive “token added mail”.

Logs

idea.log

backend.zip

[ForNeVeR]

Steps to reproduce

It looks like I was able to achieve a stable reproduction of issue in my environment. Here’s the steps to reproduce the issue:

1. Create a Git repository in your Azure DevOps account.
2. Create a local project in your IDE of choice (e.g. IDEA).
3. Select menu item VCS | Import into Version Control | Import into Azure DevOps Services Git….
4. Sign in into Azure DevOps account.
5. Select any existing project, enter a repository name, press Import.

Now, depending on IDEA version and your Git settings, you’ll encounter one of the following scenarios:

1. IDEA <= 2018.2, git with default credential manager (Windows): you’ll be asked for credentials again, everything will work afterwards. But if you cancel the first credential manager request, then see next item.
2. IDEA <= 2018.2, git without credential manager: you’ll be asked for credentials again, and again, and again; nothing will work.
3. IDEA 2019.1+: the same as 2, but git credential manager doesn’t matter; it won’t work anyway.

Bad news

As you can see, the issue is becoming more serious in more recent versions of IDEA and other IDEA-based IDEs.

The troublesome component is TfGitHttpAuthDataProvider. This component becomes active if Git asks IDEA for credentials. In IDEA 2017 and 2018, it was a rare case on Windows (only if the credential manager was manually disabled or if the user explicitly canceled the credential manager request), but it now works by default in IDEA 2019.1+, because IDEA now disables the default credential manager when the Git is started from IDEA.

In IDEA 2017, it had one problem: the format of URL it received was not the expected one. Git was sending the following URL: https://[e-mail], but the plugin expected the format https://dev.azure.com/username. The URL was successfully patched inside of an authentication flow (and that’s why the authentication seems to work), but it wasn’t patched afterwards. So, the plugin was asking the authentication mechanism to provide the credentials for URL https://[e-mail], but the mechanism only had the credentials for URL https://dev.azure.com/username.

It became even worse in IDEA 2018, because now the GitHttpAuthDataProvider interface is expanded to not pass the username by default (the plugin need to override another method to get the username).

And it became much worse around IDEA 2019, because now IDEA disables the default credential manager, so the plugin’s mechanism is suddenly always enabled.

Good news

The good news is that now we have a reproduction steps and we’re fully aware of the issue. Hopefully we’ll be able to fix it very soon. Thanks to everyone who reported here, and we’re sorry for the inconveniences caused by this issue. Please stay tuned.

[erielmiquilino]

Same issue here…

IntelliJ IDEA 2019.1 (Ultimate Edition) Build #IU-191.6183.87, built on March 27, 2019 JRE: 1.8.0_202-release-1483-b39 amd64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.0.3-200.fc29.x86_64

plugin version: 1.150.0