You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In e2e testing I've found that the axiom auth token expires very quickly so I urgently added this really bad re-auth implementation so that the testing session could continue: 87f49d2
Are you able to add a proper, elegant fix for expired auth tokens?
e.g. if when receiving the token there is an expiry time, then our client should renew before that expiry time is reached.
Or, at the very least, api requests that result in an "Unauthorized" response should transparently attempt to re-authenticate at the client lib level instead of the driver level.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
In e2e testing I've found that the axiom auth token expires very quickly so I urgently added this really bad re-auth implementation so that the testing session could continue: 87f49d2
Are you able to add a proper, elegant fix for expired auth tokens?
e.g. if when receiving the token there is an expiry time, then our client should renew before that expiry time is reached.
Or, at the very least, api requests that result in an "Unauthorized" response should transparently attempt to re-authenticate at the client lib level instead of the driver level.
The text was updated successfully, but these errors were encountered: