<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
0D51Y00009pdm4jSAAOkta Classic EngineAdministrationAnswered2024-05-16T20:05:03.000Z2020-11-05T16:18:47.000Z2021-05-18T14:02:22.000Z
  • feok4 (feok4)

    Can you post the entry from the Okta system log(s) for this user/these users?

  • bvkdd (bvkdd)

    I will look for that and get it posted shortly

  • bvkdd (bvkdd)

    It appears to be tied somehow to Office 365

    • Unknown file type
      The file is no longer available.
  • feok4 (feok4)

    Can you expand that using the black circle with the white arrow? I assume you have modern auth enabled in the tenant. Are there any sign on policies for O365 configured? Any errors under dashboard --> Tasks?

     

  • bvkdd (bvkdd)

    We recently integrated our Okta and Office 365, and this is literally the only user that continues to get locked out. When I changed my password, I simply had to enter my new password in Office to match it at the login, and never had an issue.

    • Unknown file type
      The file is no longer available.
  • feok4 (feok4)

    Alex - when you configured O365, was it for SSO (WS-Fed), provisioning, license management, etc? Was it for a single domain tenant, etc? Why i'm asking is the comment above re you changing your password to match what was in Okta.

  • bvkdd (bvkdd)

    I got this trying to force Office to use his AD password

    • Unknown file type
      The file is no longer available.
  • feok4 (feok4)

    Alex - when WS-Fed is setup, all user objects need to be managed via Okta or Active Directory, depending on how you have your environment set up.

10 of 20
This question is closed.
Loading
User keeps getting locked out