Symptoms
Connecting with a Horizon Client/View Client fails to Authenticate with a smartcard and falls back to the Windows password.Logging will record the fallback from smartcard authentication to a standard Windows password login
2023-08-09T07:56:31.708+05:30 DEBUG (19E8-11C0) <ajp-nio-127.0.0.1-8009-exec-1> [ProperoAuthFilter] (SESSION:d123_***_1ab2) Attempting to authenticate against cert-auth
2023-08-09T07:56:31.708+05:30 DEBUG (19E8-11C0) <ajp-nio-127.0.0.1-8009-exec-1> [CertificateAuthFilter] (SESSION:d123_***_1ab2) Client did not use Certificate Authentication, skipping or failing
2023-08-09T07:56:31.708+05:30 DEBUG (19E8-11C0) <ajp-nio-127.0.0.1-8009-exec-1> [CertificateAuthFilter] (SESSION:d123_***_1ab2) Failing Certificate authentication, bypassing for OPTIONAL mode
2023-08-09T07:56:31.708+05:30 DEBUG (19E8-11C0) <ajp-nio-127.0.0.1-8009-exec-1> [ProperoAuthFilter] (SESSION:d123_***_1ab2) Attempting to authenticate against windows-password
2023-08-09T07:56:31.708+05:30 DEBUG (19E8-11C0) <ajp-nio-127.0.0.1-8009-exec-1> [ProperoAuthFilter] (SESSION:d123_***_1ab2) Not authenticated, requesting login page for windows-password
<failed smartcard auth after upgrade>
Purpose
This article provides troubleshooting steps and identifies issues with Custom Control Mapping and smartcards.
Cause
Broker services get restarted after secure gateway services when we do an upgrade
Impact / Risks
SmartCard Authentication fails after upgrade
Resolution
This matter is corrected with 2309 and will not Impact an update to this release.
Workaround
After upgrading to Horizon 8.10, a restart of the VMware Horizon view security gateway component is required for smartCard Authentication to work properly.
