-
-
Notifications
You must be signed in to change notification settings - Fork 226
Enforce limit on number of devices per user #35515
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
Closed
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
6d87fb4
Create func to check for too many devices
gherceg 2c30397
Return 403 if device limit is exceeded
gherceg 2af1f45
Allow if device_id is none
gherceg cd37b50
More conservative limit of 100
gherceg 47fe879
Merge branch 'master' into gh/devices-per-user
gherceg 93e48ec
Move DEVICES_PER_USER to settings
gherceg 0b04d75
Fix test typo
gherceg f90aa81
Use datetime.now(timezone.utc)
gherceg 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
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
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
Oops, something went wrong.
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.
Can device ids be set by the submitting device? In other words, would it be possible for someone to make their mobile device(s) ids start with
WebAppsLogin
or be empty and exempt themselves from the limit? Do we care?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.
Yeah good question that I do not know the answer to off the top of my head. I can dig more into this one and get back to you.
Uh oh!
There was an error while loading. Please reload this page.
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 official CC Mobile app doesn't allow changing the device ID. Forms submitted by other means can set it to whatever they want. This makes me wonder if we need to account for API submitted forms (ignoring them)?
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 API use case is interesting because it seems far removed from the original intent behind the user metadata (last device_id used, etc) that is part of the motivation for these changes. On the other hand, it seems like using the API in a way where one user would have form submissions with differing device ids in a short time window isn't exactly expected behavior, which would make me lean towards treating API submissions the same as mobile device submissions.
FYI I'm putting together an alternative implementation for rate limiting submissions at a much shorter time window (1 minute), and will link that here once up for review.