Create Incident if inactive User tries to login

[Dominik9]

Hi experts

We have enabled the "Auto Provisioning User" for our Azure Identity Provider which automatically creates users when they log in for the first time. Now we want to set "Locked Out" to "True" for users who have not logged in for 3 months. After another 3 months we want to set "Active" to "False". If these users try to log in again, an incident should be created.

But now the situation is that when a user tries to login that is inactive, the system tries to create a new user. How can I catch this so that it doesn't try to create a new user, but realizes that there is already a user who is simply inactive?

Users that are locked out but active are detected and we can catch this directly in the transform map script. Unfortunately, this does not work for inactive users.

Does anyone have an idea?

Thanks

Dominik

[Praveen Tripath]

In Servicenow there is a functionality by which the User access auto deactivated if user seems off or Inactive from past 90 days. 

[Dominik9]

Hi Praveen 

Thank you for your respond.

This is not our problem. Our problem is that the SSO tries to create a new user if an inactive user tries to login. But we would like the system to create an incident in this case. 

Regards
Dominik

[Community Alums]

Hello @Dominik9 ,
Did you find any solution for this?

I have the same case, when inactive user tries to login, then we have to make his account as active. Currently it is creating duplicate user record with federated id.

[Dominik9]

Hi @Community Alums 

As I left the project long time ago I do not remember properly what the solution was. But I think instead creating an incident for the inactive user we implemented another process. 

In your case, can't you create a onBefore insert Business rule which checks if there is already a user, activate the existing one and abort the insert in this case?

[svirkar420]

Hello @Dominik9 , In ServiceNow users usually are made inactive when they don't have any work to do or left the environment. Once the user is made inactive he will not be able to make any kind of requests, incidents or anything into the system. Basically that person would not be even able to log in and since user will not be able to log in there is no need to make and incident for it.

If this solution helped you Please Mark this solution as accepted and helpful as it will be helpful for other users and readers as well.
Best Regards.
Saurabh V.