fix(wso2): use client_credentials as grant_type for token generation #61
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
flaviostutz
temporarily deployed
to
npmjs-registry
GitHub Actions
Inactive
flaviostutz
temporarily deployed
to
npmjs-registry
GitHub Actions
Inactive
…onstructs into fix/wrong-token-store
…so2 instances cache this
flaviostutz
temporarily deployed
to
npmjs-registry
GitHub Actions
Inactive
flaviostutz
temporarily deployed
to
npmjs-registry
GitHub Actions
Inactive
flaviostutz
temporarily deployed
to
npmjs-registry
GitHub Actions
Inactive
flaviostutz
temporarily deployed
to
npmjs-registry
GitHub Actions
Inactive
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.
Summary
API calls to the /store endpoint were failing due to not using client_credentials while generating the bearer token
This PR changes it to use client_credentials grant_type.
Breaking changes
None