Skip to main content

Passwordless Login AD Certificate Services (AD CS) CRL Issues

Issue Description​

While this issue could occur an any Active Directory Certificate Services (AD CS) environment, we’ve seen this in Cloudshare with the AD CS server. Cloudshare has a blueprint that is a pre-configured AD Domain Controller with AD CS installed together with a domain-joined Windows 10 Pro Desktop. Besides the creation of the custom certificate template, the AD CS configuration sticks with the defaults. We’ve seen occurrences of HYPR Passwordless authentication failing after having been working and it seems to be related to CRL publication expiration.

The mobile error is 101038.

The Desktop shows the message “The user name or password is incorrect.”

We’ve also seen this error:

You can try to enroll a new personal certificate on the Desktop with the Microsoft Management Console (MMC).

Steps to Reproduce​

If you see the above errors, you can confirm this is a CRL issue by gathering more information.

Errors on the Desktop​

2022-09-28 10:33:33,277 DEBUG (8432.20) Hypr.Lib.Service.Network.a = [d4e7cb8b95fcd6b3,d4e7cb8b95fcd6b3] POST https://nfield.hypr.com/rp/wsapi/client/verification/complete/25e8804ee6f98d77d2423a63e6172de5b7a3dd692d8f0a8a7086a8db80f3cdfc
2022-09-28 10:33:33,277 DEBUG (8432.20) Hypr.Lib.Service.Network.a = [d4e7cb8b95fcd6b3,d4e7cb8b95fcd6b3] Payload: {
  "authorizationCode": 403,
  "message": "Authorization was rejected status=0xC000006D",
  "sessionId": "25e8804ee6f98d77d2423a63e6172de5b7a3dd692d8f0a8a7086a8db80f3cdfc",
  "version": 2
}

Event Viewer​

Logon Failure
An account failed to log on.
 
Subject:
       Security ID:       	     SYSTEM
       Account Name:       	     WIN10PRO$
       Account Domain:       	     HYPRLAB
       Logon ID:       	     0x3E7
 
Logon Type:       	    	     2
 
Account For Which Logon Failed:
       Security ID:       	     NULL SID
       Account Name:       	     hypruser@hyprlab.net
       Account Domain:       	     
 
Failure Information:
       Failure Reason:       	     An Error occured during Logon.
       Status:       	    	     0xC000006D
       Sub Status:       	     0xC000038B
 
Process Information:
       Caller Process ID:        0x5c0
       Caller Process Name:        C:\Windows\System32\svchost.exe
 
Network Information:
       Workstation Name:        WIN10PRO
       Source Network Address:        127.0.0.1
       Source Port:       	     0
 
Detailed Authentication Information:
       Logon Process:       	     User32
       Authentication Package:        Negotiate
       Transited Services:        -
       Package Name (NTLM only):        -
       Key Length:       	     0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.
 
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
 
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
 
The Process Information fields indicate which account and process on the system requested the logon.
 
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
 
The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.

Errors on the AD CS server​

Event Viewer​

  1. Open the local Certification Authority in MMC.

  2. Double-click the Request, then select the Details tab.

  3. Click the CRL Distribution Points and in the display pane below, find the entry after "URL="; copy that value.

  4. On the AD CS server and start a command prompt. Run the following command using the URL value copied in the previous step:

    certutil -URL "ldap:///CN=hyprlab-ADSERVER-CA,CN=adserver,CN=CDP,CN=Public Key Services,CN=Services,CN=Configuration,DC=hyprlab,DC=net?certificateRevocationList?base?objectClass=cRLDistributionPoint"

  5. A window will pop up. Click the Retrieve button.



  6. Double-click the Expired Delta CRL.

    At the time the above screenshot was made, the expiration date had passed; this means the that publication failed.

Known Workarounds​

Restarting AD CS seems to fix this issue.





HYPR login gave this error:



Resolution​

Restarting AD CS may seem to fix the CRL issue, but the HYPR Passwordless client may still not work. Try rebooting the workstation and attempting to login with HYPR Passwordless again.

This related article recommends increasing the interval for publishing. Update the Cloudshare Blueprint by increasing these settings.

BEFORE:

AFTER: