Comments on: Enable passwordless security key sign-in in Hybrid Azure Active Directory environments https://inthecloud247.com/enable-passwordless-security-key-sign-in-in-hybrid-azure-active-directory-environments/ Intune, Windows, Office 365, Microsoft 365, Azure, Automation Tue, 03 Sep 2024 08:12:51 +0000 hourly 1 By: DIon https://inthecloud247.com/enable-passwordless-security-key-sign-in-in-hybrid-azure-active-directory-environments/#comment-235626 Tue, 03 Sep 2024 08:12:51 +0000 https://inthecloud247.com/?p=4608#comment-235626 In reply to Sunny.

I’m having the same issue. Dod you resolved yours?

]]> By: Ingo D. https://inthecloud247.com/enable-passwordless-security-key-sign-in-in-hybrid-azure-active-directory-environments/#comment-204440 Thu, 20 Jul 2023 03:01:37 +0000 https://inthecloud247.com/?p=4608#comment-204440 Great article, thank you!
One comment: If you’re using MFA for the cloud credentials, the command is slightly different.
$userPrincipalName = “admin@yourdomain.com”
Set-AzureADKerberosServer -Domain $domain -UserPrincipalName $userPrincipalName -DomainCredential $domainCred

]]> By: Sunny https://inthecloud247.com/enable-passwordless-security-key-sign-in-in-hybrid-azure-active-directory-environments/#comment-191861 Sun, 20 Nov 2022 04:25:57 +0000 https://inthecloud247.com/?p=4608#comment-191861 In reply to Saidul Islam.

I also have the same issue, for first time windows configuration should the laptop needs line of sight to the ad or azure ad? I get the same error Sorry, try that again. There was an issue with the server.”
Where do I check the logs of what happenned?

]]> By: Saidul Islam https://inthecloud247.com/enable-passwordless-security-key-sign-in-in-hybrid-azure-active-directory-environments/#comment-190722 Thu, 20 Oct 2022 12:07:57 +0000 https://inthecloud247.com/?p=4608#comment-190722 Hi,
I am facing the following issue after implementing this technology:
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.”

]]>