[API-215] Permanent token deprecation and client credentials support #68
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
Contributor
betacar
commented
Jan 12, 2021
betacar
commented
- Permanent tokens are no longer supported
- Client credentials can be used
githuib
reviewed
Jan 13, 2021
githuib
approved these changes
Jan 13, 2021
| { | ||
| name: 'getToken', | ||
| returnedValue: Promise.resolve({ | ||
| access_token: 'i-shall-live-and-die-at-my-post', |
betacar
added a commit
that referenced
this pull request
May 10, 2021
…68) * Permanent token support removed * Client credentials tests * Throw an exception if permanent token is used * Optional scope added to getToken method * Code coverage increased * Typofix * Typofix * Test unignored * Use the redirection URI property to know if we have client credentials or not * Test fixed
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.