starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Hide webhook bearer tokens #8881

New Issue
Closed
opened 2025-12-29 20:42:28 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:42:28 +01:00
Owner
Copy Link

Originally created by @arjenvri on GitHub (Nov 24, 2023).

NetBox version

v3.6.5

Feature type

Change to existing functionality

Proposed functionality

Add the possibility to hide webhook additional headers information for all users just having read-only rights for webhooks.
One solution would be adding an additional field for secrets that is hidden for read-only users and can be referred to as variable in the additional headers and payload configuration.

Use case

For many webhooks, headers are used for bearer token style authentication. Currently these secrets can be read by users with read-only rights, although these secrets could be sensitive.

Database changes

Add additional webhook field to store an api secret.

External dependencies

No response

Originally created by @arjenvri on GitHub (Nov 24, 2023). ### NetBox version v3.6.5 ### Feature type Change to existing functionality ### Proposed functionality Add the possibility to hide webhook additional headers information for all users just having read-only rights for webhooks. One solution would be adding an additional field for secrets that is hidden for read-only users and can be referred to as variable in the additional headers and payload configuration. ### Use case For many webhooks, headers are used for bearer token style authentication. Currently these secrets can be read by users with read-only rights, although these secrets could be sensitive. ### Database changes Add additional webhook field to store an api secret. ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:42:28 +01:00
adam closed this issue 2025-12-29 20:42:28 +01:00
adam commented 2025-12-29 20:42:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 27, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Nov 27, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:42:29 +01:00
Author
Owner
Copy Link

@arjenvri commented on GitHub (Nov 28, 2023):

@jeremystretch thank you, updated with an actionable suggestion.

@arjenvri commented on GitHub (Nov 28, 2023): @jeremystretch thank you, updated with an actionable suggestion.
adam commented 2025-12-29 20:42:29 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Dec 6, 2023):

See discussion in #14008

@arthanson commented on GitHub (Dec 6, 2023): See discussion in #14008
adam commented 2025-12-29 20:42:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 14, 2023):

It certainly seems like the use case cited here would be covered by #14008, so I'm going to close this out. Please comment under that issue if there are specific other details you'd like considered as part of that work.

@jeremystretch commented on GitHub (Dec 14, 2023): It certainly seems like the use case cited here would be covered by #14008, so I'm going to close this out. Please comment under that issue if there are specific other details you'd like considered as part of that work.
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#8881
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?