<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
0D54z0000A2BkGnCQKOkta Classic EngineAuthenticationAnswered2025-09-11T09:00:32.000Z2024-03-07T16:38:25.000Z2024-03-19T18:34:45.000Z

x4tak (x4tak) asked a question.

User How to deactivate users in OKTA after 90 days

Good Morning,

 

We are using ADFS authentication and would like to know how to deactivate Okta users after a specific time period, such as 60 or 90 days.


  • TimL.58332 (Workflows)

    @x4tak (x4tak)​  - There isn't anything built-in to Okta core to achieve this specific task. Something like this could be achieved with Okta Workflows assuming you have a queryable value that determines if your maximum time period has been met. For example when the user is first "turned on" to start the time period if then a custom attribute was updated to contain the "shut off" date in ISO 8601 format Workflows could search your user base for users that have met or exceeded this date and deactivate them.

     

    Workflows allows you to build your own solutions to edge cases you are trying to solve for. But it is only going to be able to leverage the existing API's for the vendor (in this case Okta) and the available datapoints. If datapoints that you need don't exist you may need to also build in a process to make them exist for your use case to be viable.

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    @x4tak (x4tak)​  - There isn't anything built-in to Okta core to achieve this specific task. Something like this could be achieved with Okta Workflows assuming you have a queryable value that determines if your maximum time period has been met. For example when the user is first "turned on" to start the time period if then a custom attribute was updated to contain the "shut off" date in ISO 8601 format Workflows could search your user base for users that have met or exceeded this date and deactivate them.

     

    Workflows allows you to build your own solutions to edge cases you are trying to solve for. But it is only going to be able to leverage the existing API's for the vendor (in this case Okta) and the available datapoints. If datapoints that you need don't exist you may need to also build in a process to make them exist for your use case to be viable.

    Expand Post
    Selected as Best
This question is closed.
Loading
User How to deactivate users in OKTA after 90 days