Using the UPN of an AD account as the login name to a Windows system causes SecureLogin to ask for the password again
Environment
NetIQ SecureLogin (NSL) Client 9.2 and below
Situation
When using the SAM account name to log on to a Windows system, SecureLogin starts and functions as usual. When the same AD user uses the UPN to log on to the same Windows system, NSL prompts the user for the AD password again, when entering the password NSL starts and is functional.