Hi!

In regards of this matter, I understand you and the issue you're encountering.

To be able to get to a resolution on this, I think the shortest path to a resolution would be to create a ticket on this so we can get into a screen sharing session so we double-check the flow and the use case correctly and after that do the right changes.

Please make sure to get in touch with us through a new ticket and we'll be more than happy to assist you. Looking forward for that!

All the best!

I realized after posting this issue that this was a non issue to begin with. OKTA is already sending a timestamp with a TimeZone identifier (the Z at the end of the timestamp indicates UTC). On our end the C# method DateTime.Parse("2021-08-02T22:54:52.995Z") correctly identifies this as a UTC timestamp. When I do a date comparison similar to the below code, C# automatically provides local time for comparison which is in the correct time range.

```

var notOnOrAfter = DateTime.Parse("2021-08-02T22:49:52.995Z");

bool isValid = DateTime.Now < notOnOrAfter;

```

There is no action needed here. Thanks for your response.

I cannot edit my previous response, however if someone else lands here, reference the following timestamp serialization notation

• 2009-06-15T13:45:30 (DateTimeKind.Local) --> 2009-06-15T13:45:30.0000000-07:00
• 2009-06-15T13:45:30 (DateTimeKind.Utc) --> 2009-06-15T13:45:30.0000000Z
• 2009-06-15T13:45:30 (DateTimeKind.Unspecified) --> 2009-06-15T13:45:30.0000000

the last part of the timestamp is the Time Zone Designator per ISO 8601 standards and is reserved to indicate UTC time correction. If a timestamp is properly serialized the DateTime library that you use to parse it (System.DateTime in C#) should be able to correctly parse the OKTA timestamp as a UTC timestamp and when comparing timestamps should provide local time when the object is used for comparison. If you are using some other programming language or framework that does not handle this properly consider implementing a DateTime parser that can do this for you.

References:

https://www.w3.org/TR/NOTE-datetime

https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings#table-of-format-specifiers - round-trip date/time pattern