-
-
Notifications
You must be signed in to change notification settings - Fork 253
handle an OAUTH2 offline token refresh #241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Laura Pardo <lpardo@redhat.com>
|
any updates on this? Am I missing a previous step or anything for this to get reviewed/accepted? |
kingthorin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just minor things for consistency
|
The conflict in CHANGELOG.md also needs to be addressed. |
|
To address the DCO requirement you'll need to sign-off the commit(s): |
Co-authored-by: Rick M <kingthorin@users.noreply.github.com> Signed-off-by: Laura Pardo <lpardo@redhat.com>
|
To address the DCO requirement you'll need to sign-off the commit(s): |
kingthorin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Getting close
kingthorin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
|
Thank you! |
This PR adds OAUTH2 offline token handle for ZAP users.
Authentication/OfflineTokenRefresher.js will automatically fetch the new access token for every unauthorized request determined by the "Logged Out" or "Logged In" indicator previously set in Context -> Authentication.
HTTP Sender/AddBearerTokenHeader.js will add the new access token to all requests in scope made by ZAP (except the authentication ones) as an "Authorization: Bearer [access_token]" HTTP Header.