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

Option to reference a Authentication Server #500

New Issue
Closed
opened 2025-12-29 16:22:40 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:22:40 +01:00
Owner
Copy Link

Originally created by @mbdraks on GitHub (Oct 27, 2016).

Hi,

It's possible to reference an authentication server in the device settings ?

So in addition to putting the device admin credentials it would be possible to know that the device is able to authenticate against a specific RADIUS/TACACS server.

Best Regards

Originally created by @mbdraks on GitHub (Oct 27, 2016). Hi, It's possible to reference an authentication server in the device settings ? So in addition to putting the device admin credentials it would be possible to know that the device is able to authenticate against a specific RADIUS/TACACS server. Best Regards
adam closed this issue 2025-12-29 16:22:40 +01:00
adam commented 2025-12-29 16:22:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 27, 2016):

You can easily create a custom field to do that.

@jeremystretch commented on GitHub (Oct 27, 2016): You can easily create a custom field to do that.
adam commented 2025-12-29 16:22:41 +01:00
Author
Owner
Copy Link

@mbdraks commented on GitHub (Oct 27, 2016):

Yes, that was my first thought, but from what I saw it's not possible to link to an existing device in the selection field, but I guess that the same logic would apply for things like link a ESX server to an Storage etc... So maybe the value vs complexity in this issue is low.

I'll follow through using the custom fields as suggested, thanks!

@mbdraks commented on GitHub (Oct 27, 2016): Yes, that was my first thought, but from what I saw it's not possible to link to an existing device in the selection field, but I guess that the same logic would apply for things like link a ESX server to an Storage etc... So maybe the value vs complexity in this issue is low. I'll follow through using the custom fields as suggested, thanks!
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
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#500
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?