-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Merging to release-4-lts: [TT-10189/TT-10467] Add OAuthPurgeLapsedTokens (#5766) #5901
Merging to release-4-lts: [TT-10189/TT-10467] Add OAuthPurgeLapsedTokens (#5766) #5901
Conversation
<!-- Provide a general summary of your changes in the Title above --> This PR adds an event `OAuthPurgeLapsedTokens`, which upon receiving would delete all lapsed OAuth tokens. It also adds endpoint `DELETE /tyk/oauth/tokens?scope=lapsed` to purge lapsed OAuth tokens synchronously. What are lapsed OAuth tokens? Lapsed OAuth tokens that are expired and past `oauth_token_expired_retain_period` configured in gateway config. Sub Task: https://tyktech.atlassian.net/browse/TT-10467 Parent Ticket: https://tyktech.atlassian.net/browse/TT-10189 <!-- Why is this change required? What problem does it solve? --> <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why --------- Co-authored-by: dcs3spp <[email protected]> (cherry picked from commit 6373930)
Apply Sweep Rules to your PR?
|
API tests result: skipped 🚫 |
API tests result: skipped 🚫 |
API tests result: skipped 🚫 |
API tests result: skipped 🚫 |
API tests result: skipped 🚫 |
API tests result: skipped 🚫 [TT-10189/TT-10467] Add OAuthPurgeLapsedTokens (#5766) DescriptionThis PR adds an event Related IssueSub Task: https://tyktech.atlassian.net/browse/TT-10467 Motivation and ContextHow This Has Been TestedScreenshots (if appropriate)Types of changes
Checklist
Co-authored-by: dcs3spp [email protected] Co-authored-by: Jeffy Mathew [email protected] |
…ens (#5766) (#5901) [TT-10189/TT-10467] Add OAuthPurgeLapsedTokens (#5766) <!-- Provide a general summary of your changes in the Title above --> ## Description This PR adds an event `OAuthPurgeLapsedTokens`, which upon receiving would delete all lapsed OAuth tokens. It also adds endpoint `DELETE /tyk/oauth/tokens?scope=lapsed` to purge lapsed OAuth tokens synchronously. What are lapsed OAuth tokens? Lapsed OAuth tokens that are expired and past `oauth_token_expired_retain_period` configured in gateway config. ## Related Issue Sub Task: https://tyktech.atlassian.net/browse/TT-10467 Parent Ticket: https://tyktech.atlassian.net/browse/TT-10189 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why --------- Co-authored-by: dcs3spp <[email protected]> --------- Co-authored-by: Jeffy Mathew <[email protected]>
[TT-10189/TT-10467] Add OAuthPurgeLapsedTokens (#5766)
Description
This PR adds an event
OAuthPurgeLapsedTokens
, which upon receivingwould delete all lapsed OAuth tokens.
It also adds endpoint
DELETE /tyk/oauth/tokens?scope=lapsed
to purgelapsed OAuth tokens synchronously.
What are lapsed OAuth tokens? Lapsed OAuth tokens that are expired and
past
oauth_token_expired_retain_period
configured in gateway config.Related Issue
Sub Task: https://tyktech.atlassian.net/browse/TT-10467
Parent Ticket: https://tyktech.atlassian.net/browse/TT-10189
Motivation and Context
How This Has Been Tested
Screenshots (if appropriate)
Types of changes
functionality to change)
coverage to functionality)
Checklist
why it's required
explained why
Co-authored-by: dcs3spp [email protected]