<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008G7V2SSAVOkta Classic EngineLifecycle ManagementAnswered2023-06-27T21:49:55.000Z2016-08-17T13:45:06.000Z2018-07-02T16:39:10.000Z

  • adam.lowe1.4386711186435444E12 (Okta, Inc.)

    Hello Sandesh.  There are many reasons why you might encounter a login issue like this, and I'd be happy to provide some feedback on things you can check.

     

    First, I recommend confirming the user is still AD mastered and has not been disconnected from AD, making them Okta mastered.  You can do this by navigating to Directory > People, and then clicking the user to view their profile.  You will want to ensure the profile states, "Profile mastered by Active Directory".  Alternatively, you can also navigate to Directory > Directory Integrations > Active Directory > People, and be sure you can locate the user account there.  If the user is no longer showing as AD mastered, you will need to import the account from AD into Okta.

     

    If the account is AD mastered and you're still receiving an error about invalid credentials, try testing the credentials outside of Okta.  For example, can you login to a domain joined PC with that account and using the same password?  If this is successful, we know the AD account itself is good.

     

    There's also a tool in Okta to test delegated authentication that may be helpful.  You can find this tool under Security > Authentication > Active Directory > Test Delegated Authentication.  When you use this tool, a popover window will appear where you can enter the AD username and password to confirm if authentication is successful.
    Expand Post

  • JohnT.57633 (Customer)

    I had the same issue, it turned out that the Agent running on my domain controller needed updating. Under Security > Delegated Authentication, my Agent showed disconnected...However, when I logged into the DC and opened the Okta agent it showed connected. I removed the 3.4.10 agent and installed the 3.4.12 agent and all is good now.
This question is closed.
Loading
Error: Okta user is already assigned to Active Directory user- User not able to access OKTA