Add option for anonymous requests #3
Merged
Conversation
This file contains 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
garyburgmann
approved these changes
Mar 27, 2019
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.
Adds the option for a request without any
Authorization: JWT ...header to be passed through as anAnonymousUser(per main Django auth) rather than raise an exception.This allows views to use
FirebaseAuthenticationfor authentication, but still have public / generally available views, via custom permissions.A great example is a content API for a public-facing website, allowing public, unauthenticated access to the API on a read-only basis, but requiring an admin login to
POST/PUT/DELETE, etc.The option is an opt-in, configurable via
settings. DRF_FIREBASE_AUTH.ALLOW_ANONYMOUS_REQUESTSso that default behaviour is unchanged.