Hi ​@AshenR,

In the IAM users page, can you check if an entry exists by filtering by the email of a particular user who is having the issue?

If a record returns for the email, see if the Username is something like ‘001abdcxxxxx’ (a corrupted username) instead of the correct username. Try deleting that record and attempt to login as that user again. 

Hi

It can be probelm with user defintion and directory Id value or attribute mapper for that specific Idp configuration.

Hi ​@Dihan Perera No entry is being created for the specific user on the IAM Users page.

Hi ​@knepiosko I didn't configure any attribute mapper since we're using the directory ID as the email address.

Hi ​@AshenR 

Have You tried to add “email” claim to mapper?

Hi All,

 

I have configured Azure AD authentication for an IFS Cloud customer. During testing, some users are not able to log in as expected and are encountering the following error when attempting to access the application:

 

The only thing I have noticed is that there is no IAM user entry inside the profile, and no entry has been created under the IAM Users page. Have you experienced this kind of issue before?

We have the exact same SSO problem with a user who changed her surname. We did the change first in M365 and waited that the name was changed in M365 and then in IFS Cloud we changed the User Email, Description and Directory Id in Users Details. There is no IAM User (I guess that comes automatically after user successfully logged in once)

The user can login manually when Enable Default IDP is activated, but not with SSO.

Any way to solve this?

If it is related only to some users please delete IAM user under IFS user definition and then try log on again.

Its only for some users and the IAM User section is empty. We are using Azure.

Now we get this error message only browsing the users User Detail page, Enable Default IDP is YES?

 we are using version 23.1.4

Hi ​@Kenneth Gaddnas 

You need to review mtctl logs. There should be more details. Common problem is that username value is null.

It was caused by an timeout exception on iam pod

IFS Administrator did a rollout restart of ifsapp-iam pod and tha solved it