PingID secures local and remote access to Windows servers

PingID integration for Windows login has been released as a generally available feature. It provides a step up authentication to users logging into Windows server machines with the familiar PingID flow. This includes on the fly pairing, PingID's wide range of authentication methods, and co-branding as with the standard SSO MFA flow.

PingID formally supports and has been verified only with Windows password Credential Provider (CP) as the 1st factor authentication. PingID integration for Windows login is intended only for implementations of Windows machines performing as servers, due to offline limitations. If you wish to extend its use for other default Windows CPs or to client machines as well, please contact your PingID rep.

Known issues and limitations

PIN code is not supported on Windows 10

Windows 10 does not support PIN code authentication. Refer to the following thread in the Microsoft community: https://social.msdn.microsoft.com/Forums/en-US/1b960a8a-7e21-4d64-875a-a73cfc716bd6/ngc-credential-provider-on-windows-10-crashes-inside-setstringvalue-when-wrapped?forum=windowssecurity

Possible delay loading the browser for MFA, after Windows login

After rebooting the server, there may be a 10 to 15 second delay loading the embedded browser for 2nd factor authentication, after Windows login. This symptom is due to the startup launch of services, and is more prevalent on Windows 7 than on later Windows versions.