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

Creating a rack checks for wrong permissions #3257

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

Originally created by @jeremystretch on GitHub (Jan 31, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.8
  • NetBox version: 2.7.3

Steps to Reproduce

  1. Assign a user permission to create a rack (dcim.add_rack).
  2. Log in as that user and attempt to create a rack at /dcim/racks/add/

Expected Behavior

The rack creation form should be displayed.

Observed Behavior

A 403 error (permission denied) is raised. This occurs because the URL configuration is actually pointing to RackEditView instead of RackCreateView, so Django is looking for the dcim.change_rack permission instead. (This permissions check is the only different between the two views.)

Originally created by @jeremystretch on GitHub (Jan 31, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.8 * NetBox version: 2.7.3 ### Steps to Reproduce 1. Assign a user permission to create a rack (`dcim.add_rack`). 2. Log in as that user and attempt to create a rack at `/dcim/racks/add/` ### Expected Behavior The rack creation form should be displayed. ### Observed Behavior A 403 error (permission denied) is raised. This occurs because the URL configuration is actually pointing to RackEditView instead of RackCreateView, so Django is looking for the `dcim.change_rack` permission instead. (This permissions check is the only different between the two views.)
adam added the type: bugstatus: accepted labels 2025-12-29 18:27:10 +01:00
adam closed this issue 2025-12-29 18:27:10 +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: bug
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#3257
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?