Add token exchange endpoint #841
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
changelog: add
message-dimke
approved these changes
Nov 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes proposed in this Pull Request:
This introduces a class that is able to exchange the V3 token for a V5 token.
Closes #840 .
This adds the API method for the token exchange procedure.
A separate class has been added because we need to ping the v3 endpoint
so we need the constant to point to V3. We don't want to use the Base class bc it will be removed.
Besides the endpoint, this will also be the location for the update procedure method.
Detailed test instructions:
No testing for now. This will be testable when the update procedure will be implemented.
Additional details:
This is a part of the #739
Changelog entry