In certain circumstances the timestamp presented on an AD LDS object in Identity Panel may not display as expected. Rather than showing the [UTC] timestamp from the original object it will be offset by some hours, the offset will depend on the timezone of the server connecting to the AD LDS instance.
The issue is caused by the underlying [Windows and AD LDS] interface incorrectly considering times as local rather than UTC.
In some instances this can simply be an annoyance however other times it can lead to repeated exports to change a value that will never be read back by a confirming import, resulting in an endless loop.
Option 1
Set the timezone of the server(s) running Panel Service to UTC. This will preclude any offset calculation having an impact on timestamp import or export operations.
Option 2
If an attribute flow is exporting timestamps to the LDS instance it is possible to take this into account when calculating the desired value. This is easier in Identity Panel v7 where timezone functions have been introduced.
Comments
0 comments
Please sign in to leave a comment.