Rudder

Currently the timezone of the expiration date of the API account is not specified and we have no way to know at which time it really expires unless going in event logs and open technical details (see #25723) :

Also I did not change the default expiration date which should be 1 month after the creation of the account but which has now 1 more hour because it has a different timezone; the UTC+1 timezone comes out of nowhere since I have a UTC+3 server, and a UTC+2 browser.

Also when receiving API accounts via the REST API, the expiration date does not have a ISO8601 which makes it even unclear in which timezone we are reasoning :

We should add explicit time both on the browser, visible (but not editable) by the user, and in the API.