Refactor OIDC client to include refresh token exchange #2667
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.
Desired Outcome
The OIDC client wrapper class needs updating so it can facilitate a refresh token-for-ID token exchange. Future tasks will use the updated client functionality as part of a new OIDC authentication strategy.
The new OIDC client wrapper method should take a refresh token as argument, and return a decoded ID token, along with a fresh refresh token if applicable.
Implemented Changes
client.callback
->client.get_token_with_code
client.get_token_with_refresh_token
Connected Issue/Story
CyberArk internal issue link: ONYX-26609
Definition of Done
At least 1 todo must be completed in the sections below for the PR to be
merged.
Changelog
CHANGELOG update
Test coverage
changes, or
Documentation
README
s) were updated in this PRBehavior
Security