40140 Timestamp not current ideas

[mattheworiordan]

We often get feedback from customers that they hit timestamp issues, which we do in fact have a support article about, https://support.ably.io/solution/articles/3000068941-40104-timestamp-not-current/

Firstly, this to me is a small as 99% of the time this happens because they are issuing tokens on devices, which they should not be doing. We should be offering

Secondly, if a client receives a 40140, should the client not automatically query server time and try again?

@SimonWoolf @tomczoink @paddybyers WDYT?

┆Issue is synchronized with this Jira Task by Unito

[SimonWoolf]

We should be offering

...end of this sentence was cut off?

Secondly, if a client receives a 40140, should the client not automatically query server time and try again?

That would help in the case where a lib is issuing a token for itself, but the thing is that is almost always because they're specifying a clientId in the constructor, and that case will be fixed by ably/docs#345

In the case when the issuing server and client are different (and the server time is off) there isn't really much a client can do afaict. Previous discussion ably/docs#142

[mattheworiordan]

We should be offering

...end of this sentence was cut off?

Oops, I meant to say we should include explicit advice in our support articles to consider issuing token requests on their servers, not in their clients.

Secondly, if a client receives a 40140, should the client not automatically query server time and try again?

That would help in the case where a lib is issuing a token for itself, but the thing is that is almost always because they're specifying a clientId in the constructor, and that case will be fixed by ably/docs#345

Sure, but that's not always the case, but I agree this is the most common case now. I agree ably/docs#345 will help reduce the occurrence of this now.

In the case when the issuing server and client are different (and the server time is off) there isn't really much a client can do afaict. Previous discussion ably/docs#142

Sure, but isn't that what queryTime is for?

[SimonWoolf]

In the case when the issuing server and client are different (and the server time is off) there isn't really much a client can do afaict. Previous discussion ably/docs#142

Sure, but isn't that what queryTime is for?

I'm not really following what you're suggesting the client should do? We don't currently have any mechanism for a client to tell its auth server to use a specific authOption

[mattheworiordan]

I'm not really following what you're suggesting the client should do? We don't currently have any mechanism for a client to tell its auth server to use a specific authOption

Ah, yes, I see what you're saying. So the queryTime option only applies to clients that generate their own tokes...

[sync-by-unito]

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2821