<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
0D54z00008RN5AVCA1Okta Identity EngineWorkflowsAnswered2024-02-28T19:29:02.000Z2022-11-28T13:57:55.000Z2023-04-28T21:47:44.000Z
  • TimL.58332 (Workflows)

    Hello @User15717589852053945299 (Customer)​ 

     

    First: Locked out of where?

     

    For Okta, status's are going to be based on the API column for user status's.

    https://help.okta.com/en-us/Content/Topics/users-groups-profiles/usgp-end-user-states.htm

     

    Based on your screenshot I am assuming you are receiving some sort of event payload when the user reaches the "Locked" state you are concerned about.

     

    The next question is: What does "Not Locked" look like for this scenario? What action would you usually take to "Unlock" the user? Is there an API endpoint to perform this step? If there is an API endpoint to perform this step then you would just need to identify the user & perform the action.

     

    Expand Post
  • DonF.81354 (Customer)

    Not to take away from @TimL.58332 (Workflows)​ 's suggestion, but assuming this is for Okta accounts, you can also leverage the following strategies that do not require a Workflow:

     

    Create a self-service password reset policy for your org

    • This would allow you to setup an Auto Unlock capability (after 30 minutes of being locked out, the account would auto-unlock). You can also set the threshold for failed login attempts.

    Add self-service password reset to an existing password policy

    • Although this section discusses a self-service password reset capability, the directions are extremely similar for a self-service account unlock capability

    Configure your email notifications

    • This setting allows you to choose to have admins alerted when an Okta user is locked out, user reporting of suspicious activity, etc.

     

    Hope this helps! Thanks!

     

    Expand Post
  • ErnestoM.91961 (Customer)

    I need this too and could not find an Okta action on workflows to unlock a user account (a set of them really) that is in LOCKED_OUT status. Any idea if that can be done?

    • DonF.81354 (Customer)

      Yes, there does not appear to be a card dedicated to unlocking a locked out Okta user.

       

      You can use it as a trigger however to notify you in the event that it does happen, allowing you to take action sooner.imageApart from that, you could also explore self-service account unlock (linked above) as that would also help address your request.

       

      Finally, be aware there is an API endpoint to resolve this as well, but you may need to craft that within the Workflow using your custom API action card instead. Unlock User. Take note, it does state: This operation works with Okta-sourced users. It doesn't support directory-sourced accounts such as Active Directory.

      Expand Post
  • ErnestoM.91961 (Customer)

    I figured it out. The specific card does not exist but I kind if built it using the API card as shown below. That worked fine for me

    image

    • DonF.81354 (Customer)

      Glad to hear that worked for you! Please let us know if you run into any other issues. Thanks!

This question is closed.
Loading
Workflow to unlock user account