book
Article ID: 324272
calendar_today
Updated On:
Resolution
This issue is resolved in VMware vCenter 6.7 U3g.
Workaround:
- Update the user’s Active Directory account so that sAMAccountName and UserPrincipalName match the Smart Card certificate Subject Alternative Name: Principal Name
Or
- Reissue the Smart Card certificate so that Subject Alternative Name: Principal Name matches the Active Directory sAMAccountName and UserPrincipalName
Or
Or
- Install the vSphere Client Browser Enhanced Authentication Plugin and use Windows SSPI to log in with Smart Card Credentials. Client must be on the same domain or trust the domain where vCenter is joined.
- Navigate to C:\Program Files (x86)\VMware\Enhanced Authentication Plug-in 6.7
- Merge WindowsAuthKey_x64.reg
- Open Registry Editor, navigate to
- [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\CIP]
- and change value to
"UseSmartCardPrompt"=dword:00000001