User can't login with SSO - on premise orchestrator - #216

[andrewjames (Andrew)]

Hello,

We have a user who suddenly can’t login to our production Orchestrator using SSO on Windows, but can login to our development Orchestrator fine.
This is happening in Chrome and Edge. However he is able to access it using an In-Private window.
Other systems that use SSO work fine.

This is the error:

We have tried deleting and recreating the user, and also deleting cache/cookies, but it still has the same error.

Can anyone suggest anything else?

[lrtetala (Lakshman Reddy)]

Hi @andrewjames

Check this

Orchestrator Log In Issue: User Login Failed. (#216)

AD user can not access On-Prem Orchestrator. Gets the error message #216. Issue Description: Based on the event viewer logs it is seen that User is not active. It is displayed in Orchestrator interface and have needed privileges assigned: [image] Resolution: Check Db tables for the specific user: select * from dbo.users select * from identity.AspNetUsers Check the 'IsActive' Column for the specific user in both tables. It should be set to 1 (active).Update the DB table and set IsAct…

User does not exist in any organization. Please reach out to your administrator, and ask them to add you to an organization. (#216)

Double-check if the provided credentials are correct. If you have another Administrator account in your organization, remove the user with the problem and reinvite him again. Accept he email invitation and sign in.

Regards,

[andrewjames (Andrew)]

We’re not getting that error in our EventViewer. There are no warnings/errors for the IdentityService.

[andrewjames (Andrew)]

We found the issue. The user had a saved credential in the windows Credential Manager using a different username. He deleted this credential and an now login. SSO must have been using this credential instead of the user’s current logged on AD account.