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

Ability to configure napalm_username and napalm_password on a per platform basis #2028

New Issue
Closed
opened 2025-12-29 17:21:35 +01:00 by adam · 2 comments
adam commented 2025-12-29 17:21:35 +01:00
Owner
Copy Link

Originally created by @quantumzedno on GitHub (Sep 26, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Proposed Functionality

Currently you must configure napalm_username and napalm_password in configuration.py
I would like the ability to configure these options independently when creating a platform in netbox, either as part of the optional napalm parameters already configurable when creating a platform, or with separate fields which would ideally be encrypted once configured.

Use Case

This would allow managing of various devices/platforms that do not share the same static username/password across devices and platforms. which isn't ideal for security. i.e password abc123 for cisco routers and password 321cba for aruba switches etc.

If this is already possible using the optional args field in the platform creation menu, i haven't been able to figure out how and would appreciate some clarification.
Google Group Discussion I created already: https://groups.google.com/forum/#!topic/netbox-discuss/t-qGWrlVtwM

Thank you,

Ben Lockwood

Originally created by @quantumzedno on GitHub (Sep 26, 2018). ### Issue type [x] Feature request [ ] Bug report [ ] Documentation ### Proposed Functionality Currently you must configure napalm_username and napalm_password in configuration.py I would like the ability to configure these options independently when creating a platform in netbox, either as part of the optional napalm parameters already configurable when creating a platform, or with separate fields which would ideally be encrypted once configured. ### Use Case This would allow managing of various devices/platforms that do not share the same static username/password across devices and platforms. which isn't ideal for security. i.e password abc123 for cisco routers and password 321cba for aruba switches etc. If this is already possible using the optional args field in the platform creation menu, i haven't been able to figure out how and would appreciate some clarification. Google Group Discussion I created already: [https://groups.google.com/forum/#!topic/netbox-discuss/t-qGWrlVtwM](url) Thank you, Ben Lockwood
adam added the status: duplicate label 2025-12-29 17:21:35 +01:00
adam closed this issue 2025-12-29 17:21:35 +01:00
adam commented 2025-12-29 17:21:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2018):

This has already been raised; see #2113. Whatever we end up doing will likely not be limited to the platform model specifically.

@jeremystretch commented on GitHub (Sep 26, 2018): This has already been raised; see #2113. Whatever we end up doing will likely not be limited to the platform model specifically.
adam commented 2025-12-29 17:21:35 +01:00
Author
Owner
Copy Link

@quantumzedno commented on GitHub (Sep 27, 2018):

Ah, sorry about that! My thinking on the platform model was simply because there is already some napalm config that can be done there and I figured you could always just have more platforms but in the case of globally unique passwords this could be quite a pain.

I like the ideal of having it ties to secrets in some way if you could work out how to allow decryption without introducing a security hole

Great software, I'm still quite new to the platform but would love to help out where I can.

Cheers,

Ben

@quantumzedno commented on GitHub (Sep 27, 2018): Ah, sorry about that! My thinking on the platform model was simply because there is already some napalm config that can be done there and I figured you could always just have more platforms but in the case of globally unique passwords this could be quite a pain. I like the ideal of having it ties to secrets in some way if you could work out how to allow decryption without introducing a security hole Great software, I'm still quite new to the platform but would love to help out where I can. Cheers, Ben
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: duplicate
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#2028
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?