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

Custom Script secrets management #11329

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

Originally created by @SRF-oberlicy on GitHub (Jun 30, 2025).

NetBox version

V4.2.3

Feature type

Change to existing functionality

Proposed functionality

To the existing Custom Script functionality it would be great to have a secrets management included. The idea is to store secrets as securely as hashed values and reference one or multiple of them in a custom script (either in the mask or in the code directly).

I don't have an exact idea of how to implement it in terms of code, but I guess it shouldn't be too much of a change to add.

Use case

In a lot of use cases you need to talk to third-party applications - which of course need authentication to access.
There are some limitations with "traditionall" secrets management on the host machine:

  • a master password is still needed to decrypt the password safe
  • there is no feasible place to store that master password
  • you could enter the password everytime in the mask and reference it in the code, however this does not work for scheduled jobs and is unpractical if executing frequently

Database changes

No response

External dependencies

Probably an existing secrets manager - not sure which one would be feasible.

Originally created by @SRF-oberlicy on GitHub (Jun 30, 2025). ### NetBox version V4.2.3 ### Feature type Change to existing functionality ### Proposed functionality To the existing Custom Script functionality it would be great to have a secrets management included. The idea is to store secrets as securely as hashed values and reference one or multiple of them in a custom script (either in the mask or in the code directly). I don't have an exact idea of how to implement it in terms of code, but I guess it shouldn't be too much of a change to add. ### Use case In a lot of use cases you need to talk to third-party applications - which of course need authentication to access. There are some limitations with "traditionall" secrets management on the host machine: - a master password is still needed to decrypt the password safe - there is no feasible place to store that master password - you could enter the password everytime in the mask and reference it in the code, however this does not work for scheduled jobs and is unpractical if executing frequently ### Database changes _No response_ ### External dependencies Probably an existing secrets manager - not sure which one would be feasible.
adam added the type: feature label 2025-12-29 21:43:43 +01:00
adam closed this issue 2025-12-29 21:43:43 +01:00
adam commented 2025-12-29 21:43:44 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jun 30, 2025):

@SRF-oberlicy there used to be secrets management inside NetBox but it was removed to a plugin, see: https://github.com/Onemind-Services-LLC/netbox-secrets I think this might be what you are looking for.

@arthanson commented on GitHub (Jun 30, 2025): @SRF-oberlicy there used to be secrets management inside NetBox but it was removed to a plugin, see: https://github.com/Onemind-Services-LLC/netbox-secrets I think this might be what you are looking for.
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#11329
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?