-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
[stable26] invalidate existing tokens when deleting an oauth client #37230
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
9f8f2d2
invalidate existing tokens when deleting an oauth client
individual-it 19bb66a
public interface to invalidate tokens of user
individual-it aae3ff6
adjust SettingsController tests
individual-it 774cdf5
unit tests for Manager::invalidateTokensOfUser
individual-it 3e1e6f1
added @since tag
individual-it 57c7b73
autoloaderchecker
individual-it dcab216
move mocks into private variables
individual-it cb005f6
invalidate oauth2 tokens only for seen users
individual-it 67bba35
expect invalidateTokensOfUser only be called for seen users
individual-it 40dcc08
adjust @since annotation
blizzz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
invalidate existing tokens when deleting an oauth client
Signed-off-by: Artur Neumann <[email protected]>
- Loading branch information
commit 9f8f2d27b6861ecde0b479db2a9dd3ef0d395d67
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
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.
should be run for known users, not all users, and not in user facing requests as it may take ages
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.
The same thing was merged in master and stable24 already :-/
Why would it take ages?
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.
because it will ask all connected backends to all users. not an issue on small local instance, but a factor on big setups.
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.
@blizzz do you mean using
callForSeenUsers()instead ofcallForAllUsers()?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.
yes, and ideally it runs through background jobs only
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.
@blizzz I've changed it to
callForSeenUsers()in e25b640But I think I would not put it into background jobs, because as admin I would expect the connections to be deleted immediately after I delete the oauth client and not only after a cron job eventually runs.
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.
Depending on the instance size it may cycle over x thousands of users.