MatthewH.10249 (State of Iowa) asked a question.
How can I convert a date like "133905492000000000" found in a user profile attribute (ADaccountExpires) from Active Directory to something usable in an Okta Workflow. I want to create a workflow to that can look at users about to expire by this date and send them or their managers an email to inform them before it is too late and their account gets suspended.
Hi @MatthewH.10249 (State of Iowa)​,
This was an interesting one... I think I have a solution for you, though.
I had to do some research on the time format, and found this doc from MSFT as well as this StackOverflow question.
The Active Directory stores date/time values as the number of 100-nanosecond intervals that have elapsed since the 0 hour on January 1, 1601 until the date/time that is being stored. The time is always stored in Greenwich Mean Time (GMT) in the Active Directory. - from MSFT.
Based on what I found, I came up with the following:
I then attempted to validate the result using this tool, and it appears that the result is correct and in a format that you can leverage with Okta's APIs and Workflows.
My pleasure, @MatthewH.10249 (State of Iowa)​! 😎
You can also "reverse" it in workflows like such:
Will result in same value as Bryan's start above (133905492000000000). This could be useful if you want to lets say "Only evaluate users after/before" a certain date. You could then LT/GT the AD attribute value as a number instead of translating it into a date.
This was exactly what I was going to do next so thanks for the beating me to it! 🙂
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
Hi @MatthewH.10249 (State of Iowa)​,
This was an interesting one... I think I have a solution for you, though.
I had to do some research on the time format, and found this doc from MSFT as well as this StackOverflow question.
The Active Directory stores date/time values as the number of 100-nanosecond intervals that have elapsed since the 0 hour on January 1, 1601 until the date/time that is being stored. The time is always stored in Greenwich Mean Time (GMT) in the Active Directory. - from MSFT.
Based on what I found, I came up with the following:
I then attempted to validate the result using this tool, and it appears that the result is correct and in a format that you can leverage with Okta's APIs and Workflows.