When Auto-Login is enabled, a CryptoAPI public/private key pair is generated for each Workstation (each ND user can enable AutoLogin on up to 10 PCs. When roaming profiles are used, the entire set of PCs that share the same user profile count as a single PC). The Private key is stored in the Windows Private Key Store under "C:\Users\<USERNAME>\AppData\Roaming\Microsoft\Crypto\DSS" and the public key is stored in the NetDocuments user account.
There is also a key written to the Registry at “HKEY_CURRENT_USER\Software\NetVoyage\NetDocuments” called “IntegratedLogin”. The value of this key will include the user’s ND Username preceded by the word “VAULT-”. In order for these keys to be created, the user will have to have the NetDocuments Cryptography module installed and they have to be set up as a user in Active Directory on the Network. The Private key will be located in a folder that has a seemingly random name.
If this key gets removed or corrupted, Auto-Login will stop working and you may see error messages such as “The Key does not exist” at the login page.
If you are running into issues with Auto-Login, please see our Knowledgebase article on Manually Resetting Auto-Login.
Auto-Login in Citrix
When using Auto-Login in a Citrix environment, there should be no difference to the end user. The user checks the box and it logs them in automatically. However, it will only work if you are using roaming profiles in Citrix using either a Microsoft roaming profile control or the more granular Citrix profile tools. You must roam the appdata section of the user profile. We suggest you include at least these paths:
Keywords: autologin, automated login, auto-login, single sign-on, SSO