microsoft/artifacts-keyring

Fails with no error message

Closed this issue · 3 comments

GuillaumeLeclerc commented

I'm running arch-linux and it seems I'm not missing any dependencies.

pip install -U --extra-index-url PRIVATE PRIVATE         (pt6) 

Looking in indexes: https://pypi.org/simple, https://pkgs.dev.azure.com/maluuba/philly-tools/_packaging/pt/pypi/simple/
/home/guillaume/anaconda3/envs/pt6/lib/python3.7/site-packages/artifacts_keyring/plugin.py:58: UserWarning: Choosing system dotnet over dotnetcore2 one since it is newer.
  warnings.warn("Choosing system dotnet over dotnetcore2 one since it is newer.")
[Minimal] [CredentialProvider]DeviceFlow: https://pkgs.dev.azure.com/maluuba/philly-tools/_packaging/pt/pypi/simple/
[Minimal] [CredentialProvider]ATTENTION: User interaction required. 

    **********************************************************************

    To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code PRIVATE to authenticate.

    **********************************************************************

[Information] [CredentialProvider]VstsCredentialProvider - Acquired bearer token using 'ADAL Device Code'
[Information] [CredentialProvider]VstsCredentialProvider - Attempting to exchange the bearer token for an Azure DevOps session token.
WARNING: Keyring is skipped due to an exception: Failed to get credentials: process with PID 706875 exited with code 2; additional error message:

I get a valid code and I'm able to authenticate on the browser but it fails immediately after with no error. Then, its asks for the password as if artifacts-keyring was not installed. Is there somewhere I can find logs or anything that I could use to troubleshoot that?

GuillaumeLeclerc commented

Same error on Archlinux and ubuntu 18.04 (Azure VM)

ms-lolo commented

I'm seeing this error on macOS 11.2

RuntimeError: Failed to get credentials: process with PID 28589 exited with code 2; additional error message:

github-actions commented

In order to consolidate to fewer feedback channels, we've moved suggestions and issue reporting to Developer Community.

  • 👎4