Gate Overseerr requests behind a shared PIN - #21
Merged
Conversation
- POST /rooms/:id/request now requires a shared REQUEST_PIN (the app itself is public): no PIN configured -> requests_disabled; wrong PIN -> invalid_pin; else request proceeds - frontend: Add to Overseerr prompts for the PIN once, stores it locally, re-prompts on invalid_pin - Env + .dev.vars.example: REQUEST_PIN Tested local: unset -> requests_disabled (403, closed by default).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The app is public (anyone can match), so Overseerr requests are now gated by a shared PIN — otherwise a stranger could queue downloads on your server.
POST /api/rooms/:id/request: requirespin === REQUEST_PIN. No PIN set →requests_disabled(closed by default); wrong PIN →invalid_pin.REQUEST_PINsecret (env + .dev.vars.example).Tested local: with no PIN set, requests are disabled (403). After merge, set
REQUEST_PIN(I'll do prod) to activate it for you + your partner.