Example of problematic configuration and login IDs.
Distributed.properties file configured with an Active Directory domain controller:
I have a test user whose sAMAccountName is: myeastuser
This users userPrincipalName is: [email protected]
If I try to login to the ROC with myeastuser then it generates the error above. This is because we attempt to search for the user using the userPrincipalName attribute. If a login id is supplied without the userPrincipalName value then we attempt to search for it by appending "@<user.active.directory.domain>". In this case it was looking for: [email protected]
But this user is not valid, although in my active directory environment it is a menu option for me to change the usersPrincipalName. This is another option if your active directory admin, the user, and whoever else is okay with making this change.