Pratula.69048 (Customer) asked a question.
As part of Workday integration, time zone aware terminations deprovison user access at import on the next day.
Is it possible to instead terminate to user on their END DATE at a Fixed time (say 2PM).
Time zone based on their location. Any suggestions on the flow? TIA!
@Pratula.69048 (Customer) - I'm not really sure what you are asking for here. This doesn't sound like you are looking for an Okta Workflows solution but a change in how Workday > Okta integration functions?
From a Workflows perspective you could perform "Time zone" related tasks but it would require you to normalize the data. So something along the lines of a Scheduled flow that checks for everyone that is 2 days out from their END DATE. They would also need to have an attribute that indicates their TimeZone (or some other method to determine it). You could then perform conversions and populate a table.
A second schedule flow that runs every 5 minutes could check the table for entries that are passed the "NOW" date/time. Run the deprovisioning steps, remove their entry from the table.
I was trying to say that Workday Okta integration OOTB only supports Timezone aware terminations at the next import AFTER end date. So essentially user will be terminated at the earliest on 12:01am in their time zone.
I am trying to build a workflow to terminate the user at say 4pm (user time zone) on their last day. I have an attribute location that can be used to determine the user time zone.
I am thinking how we can achieve user termination at a fixed time on their last day in the selected time zone.
Hello @Pratula.69048 (Customer) , thank you for contacting Okta Community.
This can be achieved using Workflows. Have a look at the Advanced Options section of the Set schedule options article, specifically the Timezone and the Exact time options.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
So setup a scheduled flow that checks every five minutes if the user is due deprovisioning?
Will you be able to recommend how we pick the users that have a end date put in(from business), and then have these users lined up to be deprovisioned in the flow. Thanks!
Having the workflow check every 5 minutes might be challenging, but every 30 minutes or hour might be more reasonable as most people don't end their shift at 5 minute intervals.
I would set up a group rule that populates a group when a users end date attribute is populated. When the user is added to the group, the workflow kicks off and checks to see what date and shift is their end date and populates a table with their date and end time but all in the same time zone.
Every 30-60 minutes, run the workflow to check the table to see if it's time for that user to be deactivated, deactivate them if it's their time, then remove them from the table and from the group.
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
Having the workflow check every 5 minutes might be challenging, but every 30 minutes or hour might be more reasonable as most people don't end their shift at 5 minute intervals.
I would set up a group rule that populates a group when a users end date attribute is populated. When the user is added to the group, the workflow kicks off and checks to see what date and shift is their end date and populates a table with their date and end time but all in the same time zone.
Every 30-60 minutes, run the workflow to check the table to see if it's time for that user to be deactivated, deactivate them if it's their time, then remove them from the table and from the group.