Fix client credentials authentication #52
Conversation
This file contains hidden or 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
|
Oh dear. It looks like your pull request title, body, or branch name needs a Jira ticket! Please edit the title or body to include the Jira ticket associated with this pull request, e.g. DEPLOY-404 -- this activates our Jira integration. This helps with audits, work tracking, rich feedback for acceptance criteria, etc. Thank you! If you have any questions, please contact #build-deploy-team |
tbylslpnb
force-pushed
the
fix_client_id
branch
from
1ac864b to
d8bd91f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In order to make the client credentials authentication working there is only need to add additional parameter in the token request named resource with the url of the dataverse instance