Restrict access to sensitive fields for non-superusers #478
Conversation
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
…zerMixin openwisp#448 Add reusable mixins to hide sensitive model fields from non-superusers in both admin interface and REST API. Fixes openwisp#448
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add reusable mixins to hide sensitive model fields from non-superusers in both admin interface and REST API
Fixes #448
Checklist
Reference to Existing Issue
Closes #448
Description of Changes
SensitiveFieldsAdminMixinwhich automatically hides sensitive model fields in Django admin forms for non-superusers while keeping them read only.SensitiveFieldsSerializerMixinwhich automatically removes sensitive model fields from API responses for non superusersScreenshot
N/A