RADIUS_IMPORT_GROUPS setting #33
Open
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
* This allows you to implicitly set django to be in charge of group assignments, while still keeping remote_roles setting that will still bring over the is_staff and is_superuser flags from RADIUS.
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.
This allows you to implicitly set django to be in charge of group assignments, while still keeping remote_roles setting that will still bring over the is_staff and is_superuser flags from RADIUS.
The default behavior seems to be that django-radius always sets the groups of the user to what is coming over from RADIUS regardless of if you set them or not. I wanted django to be implicitly in charge of group assignments, and ignore what RADIUS sends.