Closes #16137: Remove is_staff boolean from User model #1288

Closed
opened 2026-04-05 22:59:42 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @jeremystretch on 9/9/2025

Closes: #16137

  • Remove the is_staff boolean field from our custom User model
  • Remove the REMOTE_AUTH_STAFF_GROUPS and REMOTE_AUTH_STAFF_USERS configuration parameters
  • Introduced the IsSuperuser REST API permission to replace DRF's IsAdminUser (which evaluates is_staff)
  • Accessing UI & REST API views for RQ tasks now requires superuser permission
  • Accessing the installed plugins API view now requires superuser permission
  • Extend the RQ tasks view tests to check permissions enforcement consistently
  • RemoteUserBackend now infers is_staff from is_superuser
  • PluginMenuItem still supports the staff_only attribute, but it now maps to the is_superuser attribute on a user
  • Remove references to is_staff from the LDAP authentication docs
*Originally created by @jeremystretch on 9/9/2025* ### Closes: #16137 - Remove the `is_staff` boolean field from our custom User model - Remove the `REMOTE_AUTH_STAFF_GROUPS` and `REMOTE_AUTH_STAFF_USERS` configuration parameters - Introduced the `IsSuperuser` REST API permission to replace DRF's `IsAdminUser` (which evaluates `is_staff`) - Accessing UI & REST API views for RQ tasks now requires superuser permission - Accessing the installed plugins API view now requires superuser permission - Extend the RQ tasks view tests to check permissions enforcement consistently - `RemoteUserBackend` now infers `is_staff` from `is_superuser` - `PluginMenuItem` still supports the `staff_only` attribute, but it now maps to the `is_superuser` attribute on a user - Remove references to `is_staff` from the LDAP authentication docs
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/netbox#1288