Git credential manager does not support security key

[paulcull-msft]

Version

2.0.194-beta+819e6bc120

Operating system

Windows

OS version or distribution

WIndows 10

Git hosting provider(s)

Azure DevOps

Other hosting provider

No response

(Azure DevOps only) What format is your remote URL?

https://dev.azure.com/{org}

Can you access the remote repository directly in the browser?

Yes, I can access the repository

Expected behavior

Git credential manager allows me to use a security key, which is the only thing that my organization allows me when working from home.

Actual behavior

There is no support for security keys, which means I cannot work from home.

Logs

No logs, security key is not supported. My corporation only allows this so I cannot work from home as I am unable to login.

[Cruzillian]

Hello, it's me Phantom-J 🌹

[mjcheetham]

Version
2.0.194-beta+819e6bc120

@paulcull-msft you are running a very old version of GCM here. This is from July 2020. Please can you update to the latest Git, which should include the latest GCM.

Once updated, in order to use security keys you will want to enable authentication with the Windows broker as well as OAuth token mode for Azure DevOps.

git config --global credential.msauthUseBroker true
git config --global credential.azreposCredentialType oauth

[paulcull-msft]

Hey Matthew - thanks for the response. I was OOF until today and I'll give this a shot tonight, although I thought I updated cred manager and definitely Visual Studio when I was trying to work around this. ***@***.*** Paul Cullivan Microsoft Azure DevOps Development, Automation And Administration For further assistance try out the new bot<https://aka.ms/WindowsEngineeringAccess>. From: Matthew John Cheetham ***@***.***> Sent: Friday, November 29, 2024 3:05 AM To: git-ecosystem/git-credential-manager ***@***.***> Cc: Mention ***@***.***>; Author ***@***.***> Subject: Re: [git-ecosystem/git-credential-manager] Git credential manager does not support security key (Issue #1776) Version 2.0.194-beta+819e6bc120 @paulcull-msft<https://github.com/paulcull-msft> you are running a very old version of GCM here. This is from July 2020. Please can you update to the latest Git, which should include the latest GCM. Once updated, in order to use security keys you will want to enable authentication with the Windows broker as well as OAuth token mode for Azure DevOps. git config --global credential.msauthUseBroker true git config --global credential.azreposCredentialType oauth - Reply to this email directly, view it on GitHub<#1776 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMUHHBIIFYNAF7GEA5E4GH32DBC5BBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDONRWGI2DKNZXHCSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJRGU4DIMBVGU2TDAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDENRYGQYDANRSGA2IFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZDONRWGI2DKNZXHCTXI4TJM5TWK4VGMNZGKYLUMU>. You are receiving this email because you were mentioned. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[paulcull-msft]

Ok, so I'll do some more testing tomorrow as well. The current version of git credential-manager is 2.6.0+3c28096588.... I ran those commands and when Visual Studio asked me to authenticate on the Git Changes window it pulled up the old git credential manager that didn't support security keys. When I rebuilt I got the nuget restore UI that allowed me to use a security key. If the behavior is consistent then at least I'm unblocked. I'll try over the next few days and let you know how it goes.

[paulcull-msft]

I still have this problem and I am not prompted to use a security key. Running GCM in Visual Studio defaults to the same behavior and since VS always brings up GCM I am unable to resolve. I have updated Git to 2.47.windows.1 and that is the latest. Here's what I am doing:

…

-Launch Edge just to log in with my credentials (check work email). Works as expected, I am logged in.

-Run git config commands per the below

-Launch VS

-Connect / wait (I was writing this up when I got the GCM prompt)

-Enter email address and password

-GCM fails to connect due to lack of certificate and there is no prompt for a security key.

-Shut down VS

-Run nuget restore -nocache - prompted for security key, works as expected

-Launch VS again

-GCM launches after a minute or so, but now the UI that I associate with nuget restore (probably both are GCM) is launched and I can update with a security key

-GCM UI (below) is still present and will not allow a security key - dismiss UI

-Still fails. Below UI keeps popping up and I am unable to authenticate with a security key with the below UI. Both Git and VS are up to date. This is on VS2022. When I mention GCM UI this is what I see (and does not allow for security key for authentication): [cid:86d8007c-0d83-446e-a38e-09aaacff4809] ***@***.*** Paul Cullivan Microsoft Azure DevOps Development, Automation And Administration For further assistance try out the new bot<https://aka.ms/WindowsEngineeringAccess>. From: Paul Cullivan Sent: Tuesday, December 3, 2024 7:05 PM To: ***@***.***; git-ecosystem/git-credential-manager ***@***.***> Cc: Mention ***@***.***>; Author ***@***.***> Subject: RE: [git-ecosystem/git-credential-manager] Git credential manager does not support security key (Issue #1776) Ok, so I’ll do some more testing tomorrow as well. The current version of git credential-manager is 2.6.0+3c28096588…. I ran those commands and when Visual Studio asked me to authenticate on the Git Changes window it pulled up the old git credential manager that didn’t support security keys. When I rebuilt I got the nuget restore UI that allowed me to use a security key. If the behavior is consistent then at least I’m unblocked. I’ll try over the next few days and let you know how it goes. ***@***.*** Paul Cullivan Microsoft Azure DevOps Development, Automation And Administration For further assistance try out the new bot<https://aka.ms/WindowsEngineeringAccess>. From: Paul Cullivan Sent: Tuesday, December 3, 2024 10:11 AM To: ***@***.******@***.***>; git-ecosystem/git-credential-manager ***@***.******@***.***>> Cc: Mention ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: RE: [git-ecosystem/git-credential-manager] Git credential manager does not support security key (Issue #1776) Hey Matthew – thanks for the response. I was OOF until today and I’ll give this a shot tonight, although I thought I updated cred manager and definitely Visual Studio when I was trying to work around this. ***@***.*** Paul Cullivan Microsoft Azure DevOps Development, Automation And Administration For further assistance try out the new bot<https://aka.ms/WindowsEngineeringAccess>. From: Matthew John Cheetham ***@***.******@***.***>> Sent: Friday, November 29, 2024 3:05 AM To: git-ecosystem/git-credential-manager ***@***.******@***.***>> Cc: Mention ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: Re: [git-ecosystem/git-credential-manager] Git credential manager does not support security key (Issue #1776) Version 2.0.194-beta+819e6bc120 @paulcull-msft<https://github.com/paulcull-msft> you are running a very old version of GCM here. This is from July 2020. Please can you update to the latest Git, which should include the latest GCM. Once updated, in order to use security keys you will want to enable authentication with the Windows broker as well as OAuth token mode for Azure DevOps. git config --global credential.msauthUseBroker true git config --global credential.azreposCredentialType oauth — Reply to this email directly, view it on GitHub<#1776 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMUHHBIIFYNAF7GEA5E4GH32DBC5BBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDONRWGI2DKNZXHCSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJRGU4DIMBVGU2TDAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDENRYGQYDANRSGA2IFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZDONRWGI2DKNZXHCTXI4TJM5TWK4VGMNZGKYLUMU>. You are receiving this email because you were mentioned. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[paulcull-msft]

I still have this issue. Both git and VS are updated to the latest versions (git 2.48.1.windows.1). Repro steps:

…

-Launch VS 2022 -Select clone a repo -Select Azure DevOps -Login prompt appears - select other ways to log in, select pin or security key, login successfully, get false hope -Deselect allow my organization to manage my device -Wait for the organization/project/repo you want to appear and select clone -Different UI for GCM appears with no security key option Let me know if you need anything else from me. [cid:61dd099c-4eeb-4121-9215-9e24b09aa431] Paul Cullivan Microsoft Azure DevOps Development, Automation And Administration For further assistance try out the new bot<https://aka.ms/WindowsEngineeringAccess>.

________________________________ From: Paul Cullivan Sent: Friday, December 6, 2024 11:01 AM To: ***@***.*** ***@***.***>; git-ecosystem/git-credential-manager ***@***.***> Cc: Mention ***@***.***>; Author ***@***.***> Subject: RE: [git-ecosystem/git-credential-manager] Git credential manager does not support security key (Issue #1776) I still have this problem and I am not prompted to use a security key. Running GCM in Visual Studio defaults to the same behavior and since VS always brings up GCM I am unable to resolve. I have updated Git to 2.47.windows.1 and that is the latest. Here's what I am doing:

-Launch Edge just to log in with my credentials (check work email). Works as expected, I am logged in.

-Run git config commands per the below

-Launch VS

-Connect / wait (I was writing this up when I got the GCM prompt)

-Enter email address and password

-GCM fails to connect due to lack of certificate and there is no prompt for a security key.

-Shut down VS

-Run nuget restore -nocache - prompted for security key, works as expected

-Launch VS again

-GCM launches after a minute or so, but now the UI that I associate with nuget restore (probably both are GCM) is launched and I can update with a security key

-GCM UI (below) is still present and will not allow a security key - dismiss UI

-Still fails. Below UI keeps popping up and I am unable to authenticate with a security key with the below UI. Both Git and VS are up to date. This is on VS2022. When I mention GCM UI this is what I see (and does not allow for security key for authentication): [cid:86d8007c-0d83-446e-a38e-09aaacff4809] ***@***.*** Paul Cullivan Microsoft Azure DevOps Development, Automation And Administration For further assistance try out the new bot<https://aka.ms/WindowsEngineeringAccess>. From: Paul Cullivan Sent: Tuesday, December 3, 2024 7:05 PM To: ***@***.***; git-ecosystem/git-credential-manager ***@***.***> Cc: Mention ***@***.***>; Author ***@***.***> Subject: RE: [git-ecosystem/git-credential-manager] Git credential manager does not support security key (Issue #1776) Ok, so I’ll do some more testing tomorrow as well. The current version of git credential-manager is 2.6.0+3c28096588…. I ran those commands and when Visual Studio asked me to authenticate on the Git Changes window it pulled up the old git credential manager that didn’t support security keys. When I rebuilt I got the nuget restore UI that allowed me to use a security key. If the behavior is consistent then at least I’m unblocked. I’ll try over the next few days and let you know how it goes. ***@***.*** Paul Cullivan Microsoft Azure DevOps Development, Automation And Administration For further assistance try out the new bot<https://aka.ms/WindowsEngineeringAccess>. From: Paul Cullivan Sent: Tuesday, December 3, 2024 10:11 AM To: ***@***.******@***.***>; git-ecosystem/git-credential-manager ***@***.******@***.***>> Cc: Mention ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: RE: [git-ecosystem/git-credential-manager] Git credential manager does not support security key (Issue #1776) Hey Matthew – thanks for the response. I was OOF until today and I’ll give this a shot tonight, although I thought I updated cred manager and definitely Visual Studio when I was trying to work around this. ***@***.*** Paul Cullivan Microsoft Azure DevOps Development, Automation And Administration For further assistance try out the new bot<https://aka.ms/WindowsEngineeringAccess>. From: Matthew John Cheetham ***@***.******@***.***>> Sent: Friday, November 29, 2024 3:05 AM To: git-ecosystem/git-credential-manager ***@***.******@***.***>> Cc: Mention ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: Re: [git-ecosystem/git-credential-manager] Git credential manager does not support security key (Issue #1776) Version 2.0.194-beta+819e6bc120 @paulcull-msft<https://github.com/paulcull-msft> you are running a very old version of GCM here. This is from July 2020. Please can you update to the latest Git, which should include the latest GCM. Once updated, in order to use security keys you will want to enable authentication with the Windows broker as well as OAuth token mode for Azure DevOps. git config --global credential.msauthUseBroker true git config --global credential.azreposCredentialType oauth — Reply to this email directly, view it on GitHub<#1776 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMUHHBIIFYNAF7GEA5E4GH32DBC5BBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDONRWGI2DKNZXHCSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJRGU4DIMBVGU2TDAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDENRYGQYDANRSGA2IFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZDONRWGI2DKNZXHCTXI4TJM5TWK4VGMNZGKYLUMU>. You are receiving this email because you were mentioned. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[strekill]

Hi,
got same issue in 2026 :(