Forum Discussion
ADFS - Unable to log on with UPN
Hi All,
In our development environment we have ADFS 3.0 servers authenticating federated users. Recently, users have been unable to log on using their UPN. SamAaccountName works without issue. For information the domain and upn set up is as follows:
The internal domain is childdomain.root.int.ac.uk
Users exist in the child domain "childdomain.root.int.ac.uk" but have a their UPN changed to username@int.ac.uk.
When signing into Office 365 or via ADFS theya re able to use their samaccountname but using the UPN gives an incorrect username or password error.
We see the following error in the ADFS logs:
Token validation failed.
Additional Data
Token Type:
http://schemas.microsoft.com/ws/2006/05/identitymodel/tokens/UserName
%Error message:
If they attempt to use the ADFS password change page I see the following error in the logs:
Password change failed for following user:
Additional Data
User:
u1234560@int.ac.uk.
Device Certificate:
Server on which password change was attempted:
Error details:
UserNotFound
Any ideas what might be causing this?
13 Replies
Currently we facing the same problem as your, can you share with me how you have fixed?
Can your users not login with their UPN's or are you having issues with the Password Reset URL in ADFS?
Hi,
The user can not login with their UPN's and gives an incorrect username or password error.
But they are able to logon with SAMAccountname (domain\username) format.
Thanks,
You most likely need to adjust the claims rules to pick up the changed UPN format.
Can you elaborate a little Vasil? The authentication fails completely and claims are not released. The ADFS forms authentication page just rejects the password unless you use the samaccountname format. our production environment is essentially the same and we dont have a similar issue so its quite puzzling.
Hi David
DId you come right here? I saw something similar many years ago.. You might need to alter the claims to support the multiple UPN suffixes. Did you set up the ADFS with the AADConnect wizard? I'm assuming the new UPN name space is federated and you are using it for Azure/O365
