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

Replace AUTH_EXEMPT_PATHS setting with a view-specific control #9846

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

Originally created by @jeremystretch on GitHub (Jun 14, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.0.5

Feature type

Change to existing functionality

Proposed functionality

NetBox includes a LOGIN_REQUIRED configuration parameter: When enabled, authentication is enforced for all UI views except those with URL paths matching an entry in settings.AUTH_EXEMPT_PATHS.

This issue proposes replacing the static AUTH_EXEMPT_PATHS setting with a dynamic mechanism implemented on individual views which can be used to override enforcement of the global LOGIN_REQUIRED parameter on a per-view basis. The most reliable means of implementation is probably to have the relevant views each register themselves in the global registry, and tweak the current middleware logic to reference the registry instead of the static setting. However, alternative implementations may also be considered.

Use case

Shifting from a static form of declaration to a dynamic one will enable plugins to exempt their own views from LOGIN_REQUIRED enforcement.

Database changes

None

External dependencies

None

Originally created by @jeremystretch on GitHub (Jun 14, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.0.5 ### Feature type Change to existing functionality ### Proposed functionality NetBox includes a [`LOGIN_REQUIRED`](https://netboxlabs.com/docs/netbox/en/stable/configuration/security/#login_required) configuration parameter: When enabled, authentication is enforced for all UI views except those with URL paths matching an entry in [`settings.AUTH_EXEMPT_PATHS`](https://netboxlabs.com/docs/netbox/en/stable/configuration/security/#login_required). This issue proposes replacing the static `AUTH_EXEMPT_PATHS` setting with a dynamic mechanism implemented on individual views which can be used to override enforcement of the global `LOGIN_REQUIRED` parameter on a per-view basis. The most reliable means of implementation is probably to have the relevant views each register themselves in the global registry, and tweak the current middleware logic to reference the registry instead of the static setting. However, alternative implementations may also be considered. ### Use case Shifting from a static form of declaration to a dynamic one will enable plugins to exempt their own views from `LOGIN_REQUIRED` enforcement. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 21:23:29 +01:00
adam closed this issue 2025-12-29 21:23:29 +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 status: accepted type: feature
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#9846
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?