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

Users should be able to edit/delete their own API tokens in the UI without explicit permission to do so #7507

New Issue
Closed
opened 2025-12-29 20:24:29 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:24:29 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jan 13, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.4.2

Python version

3.8

Steps to Reproduce

  1. Create a new user with no group or permission assignments.
  2. Log into NetBox as that user.
  3. Navigate to "API tokens" under the user menu at top right.
  4. Create a new API token.
  5. Attempt to edit or delete the token.

Expected Behavior

A user should be able to manage his or her own API tokens via the UI.

Observed Behavior

Users can create their own API tokens, but no ability to edit or delete them is offered without an administrator needing to assign the explicit permission to do so.

Originally created by @jeremystretch on GitHub (Jan 13, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.4.2 ### Python version 3.8 ### Steps to Reproduce 1. Create a new user with no group or permission assignments. 2. Log into NetBox as that user. 3. Navigate to "API tokens" under the user menu at top right. 4. Create a new API token. 5. Attempt to edit or delete the token. ### Expected Behavior A user should be able to manage his or her own API tokens via the UI. ### Observed Behavior Users can create their own API tokens, but no ability to edit or delete them is offered without an administrator needing to assign the explicit permission to do so.
adam added the type: bugstatus: accepted labels 2025-12-29 20:24:29 +01:00
adam closed this issue 2025-12-29 20:24:29 +01:00
adam commented 2025-12-29 20:24:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 25, 2023):

Fixed in 6f74c5ec03

@jeremystretch commented on GitHub (Jan 25, 2023): Fixed in 6f74c5ec03305b7f597a839d35b2ee0c0e8f75ad
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#7507
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?