If 2 instance obtain token with the same credentials, will one instance get kicked out during token renewal?
For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
5
●2 ●2 ●4
Token Issue
Hi @zoe ,
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If so please can you click the 'Accept' text next to the appropriate reply? This will guide all community members who have a similar question.
Thanks,
AHS
Hi,
Please be informed that a reply has been verified as correct in answering the question, and marked as such.
Thanks,
AHS
79.2k
●251 ●52 ●74
Thank you for reaching out to us.
Yes, this is a limitation of the Account authorization V1 (Machine ID, Password, and Client ID).
There is only one valid refresh token at a time. If the second instance uses the same credentials to get tokens, the previous refresh token owned by the first instance will be invalidated. Therefore, the first instance can't use to renew an access token. Then, the first instance must use the Authorization V1 credentials to get a new refresh and access token. Consequently, the refresh token owned by the second instance will be invalidated.
In conclusion, each instance that uses the same Authorization V1 credentials will compete for a valid refresh token.
This issue doesn't happen with the account authorization V2 (Client ID and Client Secret).
5
●2 ●2 ●4
@Jirapongse can I migrate to V2? any document for mirgration. Thansk!
You need to get the new V2 credentials.
For more information, please refer to this Changes to Customer Identity and Access Management: Refinitiv Real-Time - Optimized and Data Platform article.
