We have to send the account expires date to the AD “Accountexpires” which it is doing however it is creating the next day instead of the date that is sent 1/1/2024 but is posting 1/2/2024 12:00:00 AM UTC instead. any ideas how to keep the dame date on the AD on what is being sent from IDN.
This actually appears to be working correctly, from the outside perspective. If the worker’s contract ends on 6/31/24, their account shouldn’t expire at 12am on 6/31 because then they wouldn’t be able to work that day.
Is 6/31 the last day this person is working, or is 6/30 the last day they’re working?
You may want to take a look at the below document on syncing the accountexpires attribute
We have converted AD source timezone to epoch and made the identity attribute in epoch format to fix the attribute sync issue with the accountexpires attribute.
Good call out on the date thing for June as well yest typically the end date should be the last day but i do not think business thinks it that way. let me do some more testing and read on this but please keep the ideas or testing comming
So i did the test on a new date change with VAILD dates and it look to stay at the same date as set and expire at midnight. WE are all good. I need this long weekend to come faster. Thanks all