Blog Post

Core Infrastructure and Security Blog
10 MIN READ

How-to: Password-less FIDO2 Security Key Sign-in to Windows 10 HAADJ Devices

LijuV's avatar
LijuV
Icon for Microsoft rankMicrosoft
Jun 03, 2020
Hello everyone, my name is Liju and I am a Premier Field Engineer specializing in Active Directory and Azure AD. Fido2 support for single sign-on (SSO) was introduced first for cloud resources, and...
Updated Jun 03, 2020
Version 5.0
LijuVarghese
SaidulShakil's avatar
SaidulShakil
Copper Contributor
Oct 08, 2022

LijuV Bpatin Here are the logs from Kerberos from client side -

The Kerberos client could not locate a domain controller for domain OurDomainName: 0xC000005E. Kerberos authentication requires communicating with a domain controller.

The service principal name (SPN) krbtgt/NT Authority@OurDomainName is not registered, which caused Kerberos authentication to fail: 0x7. Use the setspn command-line tool to register the SPN.

Here is the log from WebAuthN:

WebAuthN Ctap GetAssertion completed.

TransactionId: {6f203a33-07a5-4d7a-ba04-ffd8075118eb}
Error: 0x8007052E. The user name or password is incorrect.

Even though the ID and Password are correct.

When connected to vpn, I can lock the PC and then can unlock the PC with Key. After couple of hours the same issue can't login with the following error  "Sorry, try that again. There was an issue with the server."