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

API key not related to Netbox user, but for system account to automate stuff #9400

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

Originally created by @RemcoVroman on GitHub (Mar 28, 2024).

NetBox version

v3.7.2

Feature type

New functionality

Proposed functionality

Let the admin users create a api key for automation purposes and is not related to a netbox user. With the API key there should be a description possebility to register what the key is for. Also the rights and experation date should be possible.

Use case

We will use this for automation purposes. The api kesy are now related to a person who might leave the organisation and then the key becomes invallid. However the automation process will need to continue.

Database changes

No response

External dependencies

No response

Originally created by @RemcoVroman on GitHub (Mar 28, 2024). ### NetBox version v3.7.2 ### Feature type New functionality ### Proposed functionality Let the admin users create a api key for automation purposes and is not related to a netbox user. With the API key there should be a description possebility to register what the key is for. Also the rights and experation date should be possible. ### Use case We will use this for automation purposes. The api kesy are now related to a person who might leave the organisation and then the key becomes invallid. However the automation process will need to continue. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:49:21 +01:00
adam closed this issue 2025-12-29 20:49:21 +01:00
adam commented 2025-12-29 20:49:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 28, 2024):

This is not feasible: All permission controls and change logging in NetBox is built on the user & group models. You simply need to create a "system" account to which API tokens can be assigned.

@jeremystretch commented on GitHub (Mar 28, 2024): This is not feasible: All permission controls and change logging in NetBox is built on the user & group models. You simply need to create a "system" account to which API tokens can be assigned.
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 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#9400
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?