Decouple REMOTE_AUTH_SUPERUSERS and REMOTE_AUTH_STAFF_USERS from REMOTE_AUTH_GROUP_SYNC_ENABLED #5613

Closed
opened 2025-12-29 19:30:09 +01:00 by adam · 2 comments
Owner

Originally created by @cova-fe on GitHub (Nov 4, 2021).

NetBox version

v3.0.8

Feature type

Change to existing functionality

Proposed functionality

According to the documentation, REMOTE_AUTH_SUPERUSERS and REMOTE_AUTH_STAFF_USERS requires REMOTE_AUTH_GROUP_SYNC_ENABLED to be true to be used. However, I don't see why, as there could use cases where we don't have any remote group but remote users that must be superusers or staff. So I decoupled the variables from group sync enabled

Use case

This could be useful when no group info is provided but we need some users to be in staff or superuser status.
my specific case is because I use GCP IAP auth via header JWT token, that does not provide any group info.

Discussion reference:
https://github.com/netbox-community/netbox/discussions/7716

(thnks @mtinberg)

Database changes

No response

External dependencies

No response

Originally created by @cova-fe on GitHub (Nov 4, 2021). ### NetBox version v3.0.8 ### Feature type Change to existing functionality ### Proposed functionality According to the documentation, REMOTE_AUTH_SUPERUSERS and REMOTE_AUTH_STAFF_USERS requires REMOTE_AUTH_GROUP_SYNC_ENABLED to be true to be used. However, I don't see why, as there could use cases where we don't have any remote group but remote users that must be superusers or staff. So I decoupled the variables from group sync enabled ### Use case This could be useful when no group info is provided but we need some users to be in staff or superuser status. my specific case is because I use GCP IAP auth via header JWT token, that does not provide any group info. Discussion reference: https://github.com/netbox-community/netbox/discussions/7716 (thnks @mtinberg) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:30:09 +01:00
adam closed this issue 2025-12-29 19:30:09 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 11, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jan 11, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Feb 10, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Feb 10, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5613