starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

[PR #5771] [CLOSED] Add the ability to Sync netbox user Groups and special Privileges with an Remote (HTTP) Auth Backend #13058

New Issue
Closed
opened 2025-12-29 22:25:10 +01:00 by adam · 0 comments
adam commented 2025-12-29 22:25:10 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/5771
Author: @MaxRink
Created: 2/9/2021
Status: ❌ Closed

Base: develop ← Head: remote_groups

📝 Commits (4)

  • 4b1979f Add Remote Group Support to the RemoteUserAuth Backend and Middleware
  • 273aec2 fix incorrect assumption about when to run the group sync
  • 6763363 Add documentation for new Settings
  • 1c67c60 format to autopep8 compliance

📊 Changes

4 files changed (+259 additions, -26 deletions)

View changed files

📝 docs/configuration/optional-settings.md (+56 -0)
📝 netbox/netbox/authentication.py (+133 -23)
📝 netbox/netbox/middleware.py (+63 -3)
📝 netbox/netbox/settings.py (+7 -0)

📄 Description

Improves upon https://github.com/netbox-community/netbox/issues/2328

Unlike the LDAP Backend, the RemoteUserBackend wasnt able to Sync Group memberships form the auth Provider.
This brings it up to parity, as the new Settings give you the Option to setup an automatic Group Sync (and revocation) on each User login.
This has been tested with oauth2-proxy
The old behaviopur of just Syncing Users and then manually managing Groups should be unaffected.
ToDo:

  • Tests for new Settings

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/5771 **Author:** [@MaxRink](https://github.com/MaxRink) **Created:** 2/9/2021 **Status:** ❌ Closed **Base:** `develop` ← **Head:** `remote_groups` --- ### 📝 Commits (4) - [`4b1979f`](https://github.com/netbox-community/netbox/commit/4b1979f7410b2bb18af6d3fe26090a69ce48526e) Add Remote Group Support to the RemoteUserAuth Backend and Middleware - [`273aec2`](https://github.com/netbox-community/netbox/commit/273aec2321ec4731bbdb7eca762ec1b36a59118b) fix incorrect assumption about when to run the group sync - [`6763363`](https://github.com/netbox-community/netbox/commit/676336364e82b6f0c255391726641892852486bc) Add documentation for new Settings - [`1c67c60`](https://github.com/netbox-community/netbox/commit/1c67c6080407318430eb406f27f3144a1c2adda8) format to autopep8 compliance ### 📊 Changes **4 files changed** (+259 additions, -26 deletions) <details> <summary>View changed files</summary> 📝 `docs/configuration/optional-settings.md` (+56 -0) 📝 `netbox/netbox/authentication.py` (+133 -23) 📝 `netbox/netbox/middleware.py` (+63 -3) 📝 `netbox/netbox/settings.py` (+7 -0) </details> ### 📄 Description ### Improves upon https://github.com/netbox-community/netbox/issues/2328 Unlike the LDAP Backend, the RemoteUserBackend wasnt able to Sync Group memberships form the auth Provider. This brings it up to parity, as the new Settings give you the Option to setup an automatic Group Sync (and revocation) on each User login. This has been tested with [oauth2-proxy](https://github.com/oauth2-proxy/oauth2-proxy) The old behaviopur of just Syncing Users and then manually managing Groups should be unaffected. ToDo: - [ ] Tests for new Settings --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 22:25:10 +01:00
adam closed this issue 2025-12-29 22:25:11 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#13058
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?