feat: ability to refresh tokens for oauth flows #4302
Merged
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.
Fixes HFE-548
Changes
This PR adds the ability to refresh generated oauth tokens. We only enable refresh tokens for the
AuthCode
flow. for other flows it doesnt make much sense to add refresh token flows as per my reading. ( but incase we get user requests, we can easily add that ).The support for the OAuth 2 authorization type is extended to the CLI, relevant business logic to derive
Authorization
headers already existed but a request with the Authorization type set tooauth-2
was blocked previously reporting a status code of501
which is changed herewith. This was also the case with themultipart/form-data
content type which is enabled along with. Necessary updates are made to the test suite aimed at increasing coverage along with the relevant fixture additions.