Access token expiration timestamps now past MySql timestamp type's maximum value

[Andrew Gilmartin]

Over the weekend we got bitten by the access token's expiration timestamp now being past 2038-01-19 03:14:07 UTC. This time is the maximum value a MySql timestamp can hold. Not an ORCID.org problem, but others might be experience this too and so perhaps ORCID.org could reduce the expiration to under 2038-01-19 03:14:07 UTC while we fix our code.

-- Andrew

[Simpson, Will]

Hi Andrew,

Thanks for letting us know about the MySql limit.

For the mailing list, the token expiration is 'now' + 20 years. So, of course newly issued long lived tokens are now over the max in MySql.

I'm investigating now to see if we can configure or patch to reduce the expiration time.

Best.

Will

On Mon, Jan 22, 2018 at 1:56 PM, Andrew Gilmartin <agilm...@crossref.org> wrote:

Over the weekend we got bitten by the access token's expiration timestamp now being past 2038-01-19 03:14:07 UTC. This time is the maximum value a MySql timestamp can hold. Not an ORCID.org problem, but others might be experience this too and so perhaps ORCID.org could reduce the expiration to under 2038-01-19 03:14:07 UTC while we fix our code.

-- Andrew

--
You received this message because you are subscribed to the Google Groups "ORCID API Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orcid-api-users+unsubscribe@googlegroups.com.
To post to this group, send email to orcid-api-users@googlegroups.com.
Visit this group at https://groups.google.com/group/orcid-api-users.
For more options, visit https://groups.google.com/d/optout.

--

Will Simpson

Tech Lead, ORCID

w.si...@orcid.org

http://orcid.org/0000-0003-4654-1403

PGP/GPG/OpenGPG key: https://keys.mailvelope.com/pks/lookup?op=get&search=0xDB70FC8C8F326A95

[Simpson, Will]

Hi Andrew,

I've configured sandbox.orcid.org to use 'now' + 19 years and 11 months as the expiration time for long live tokens.

Can you take a look on there and see if that works for you?

Best,

Will

[Andrew Gilmartin]

> Can you take a look on there and see if that works for you?

We have applied a workaround to the problem on our production servers: We just cap the expiration value at 2038-01-01. Our real fix is to move to MySql's datetime. Nevertheless, I will test your sandbox change and see if it would have helped us.

-- Andrew

[Andrew Gilmartin]

I can confirm that the 'now' + 19 years and 11 months works for our code. -- Andrew

[Will Simpson]

Fantastic, thanks for letting us know.

If anyone else on the mailing list is having a similar problem I will push the config change to production ORCID.

So, anyone else please let us know!

Best,

Will