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
Currently, a client has to request a temporal access token with the API token. This token expires and the client's request fails with 401 error. Sometimes, it causes losing data because the sent data is already read from a stream or buffer.
Possible solution
A temporal access token has more disadvantages than advantages. We can make it optional and remove it in version 1.0.
Additional context
All SDKs should stop using the temporal access token as soon as possible.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Current problem
Currently, a client has to request a temporal access token with the API token. This token expires and the client's request fails with 401 error. Sometimes, it causes losing data because the sent data is already read from a stream or buffer.
Possible solution
A temporal access token has more disadvantages than advantages. We can make it optional and remove it in version 1.0.
Additional context
All SDKs should stop using the temporal access token as soon as possible.
Code of Conduct
The text was updated successfully, but these errors were encountered: