Lazily get token for clients

[mattheworiordan]

It seems that the Java and JS libs obtain tokens automatically if token authentication is required for the client (authUrl specified for example), even if autoConnect is false.

I think this is wrong. Why obtain a token until it's needed?

┆Issue is synchronized with this Jira Task by Unito

[SimonWoolf]

It seems that the Java and JS libs obtain tokens automatically if token authentication is required for the client (authUrl specified for example), even if autoConnect is false.

Can't speak to the java lib, but for the JS lib, I can assure you it doesn't, not sure why you and Srushtika are convinced otherwise. The client lib constructor does nothing that triggers getting an auth token, it's all done the first time something (a rest request or a connect()) calls getAuthParams() or getAuthHeaders().

I've just tried it as a sanity check; it really doesn't.

[mattheworiordan]

not sure why you and Srushtika are convinced otherwise

Because that is what @paddybyers told me, and he wrote both the libs initially 😄

The client lib constructor does nothing that triggers getting an auth token, it's all done the first time something (a rest request or a connect()) calls getAuthParams() or getAuthHeaders().

Great, that's what it should do. So this is perhaps just a Java issue if Java doesn't do this @paddybyers? Is it worth clarifying in the spec given most of the libs probably behave as they should then?

[paddybyers]

So this is perhaps just a Java issue if Java doesn't do this @paddybyers?

In fact the java library does it lazily as well.

Is it worth clarifying in the spec given most of the libs probably behave as they should then?

There's nothing in the spec that says explicitly one way or the other. I think it is probably worth clarifying.

[tomczoink]

@mattheworiordan is this still something we're wanting to clarify in the spec?

[sync-by-unito]

➤ Automation for Jira commented:

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