[Feat][WRS-2231]: Introduce schema definition for OAuth 2.0 JWT Bearer #94
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
psamusev
requested review from
brapoprod,
alexandraFlavia9,
pietervp,
Matthiee and
Dvergar
as code owners
Use PR connector-cli packageTarball can be downloaded from https://cdnepgrafxstudiodev.azureedge.net/sdk/connector-cli/dev-packages/94/connector-cli.tgz To use in local project, change package.json to use local tarball "devDependencies": {
"@chili-publish/connector-cli": "https://cdnepgrafxstudiodev.azureedge.net/sdk/connector-cli/dev-packages/94/connector-cli.tgz"
} |
alexandraFlavia9
previously approved these changes
Jan 20, 2025
alexandraFlavia9
previously approved these changes
Jan 20, 2025
psamusev
changed the title
…-for-OAuth-2.0-JWT-Bearer-Token-authentication
psamusev
changed the title
psamusev
deleted the
feature/WRS-2231-Introduce-schema-definition-for-OAuth-2.0-JWT-Bearer-Token-authentication
branch
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.
To support flexibility for OAuth2.0 JWT Bearer schema approach was introduced to define for each connector own definition of required fields: jwtTokenPayload, requestBodyParams and jwtTokenParamName
In context of this PR Google Sheets connector was also updated to support new approach
Other changes:
set-authcommandOAuth2AuthorizationCodeandOAuth2ResourceOwnerPasswordduringset-authexecutionIMPORTANT: Do not merge until backend is ready and merged