feat: use the new API (POST /getToken
) for tokenUrl. and improve token renew.
#154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes
tokenUrl
parameter. Now it hitsPOST /getToken
. Requiresagora-token-service
higher than or equal to: v1.4.1. (both RTC & RTM)Pull request checklist
Please check if your PR fulfills the following requirements:
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Previously it was hitting the old Deprecated API Endpoints for generating tokens via the optional
tokenUrl
parameter.Issue Number: N/A
What is the new behavior?
Currently it will be hitting the new API Endpoint which is
POST /getToken
Does this introduce a breaking change?
Yes
No
Impact:
Users who are using the old
agora-token-service
(older than v1.4.1) which doesn't have thePOST /getToken
endpoint and using thetokenUrl
parameter for authentication purposes will be having a breaking feature.