SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-11 10:41:45 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Feature Request: Add Hardware Key or PKI Card Support for Client Authentication #1432

New Issue
Open
opened 2025-11-20 05:30:15 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:30:15 -05:00
Owner
Copy Link

Originally created by @TKaluza on GitHub (Nov 20, 2024).

Is your feature request related to a problem? Please describe.
Currently, the Netbird client supports login via website and SSO, which is efficient for administration. However, for the actual client network connection functionality, it lacks support for direct hardware-based authentication methods. This can be a limitation in environments that prioritize physical security measures or use Public Key Infrastructure (PKI) for enhanced access control. Users who rely on hardware keys or PKI cards, such as YubiKeys, Nitrokeys, or smartcards, may find the existing process inconvenient or not aligned with their security protocols.

Describe the solution you'd like
I would like the Netbird client to "natively" (or as good as possible 😉 ) support hardware-based authentication methods, allowing users to authenticate directly using devices like FIDO2 keys (YubiKey, Nitrokey) or PKI-enabled smart cards.
This feature should be an alternative or addition for the functionality of the "Setup-Keys":

  • Authentication for connecting: Using the hardware device for login, with an optional PIN requirement for additional security.
  • Compatibility: Support for a range of devices, including USB, NFC, and Bluetooth-enabled keys, as well as PKI tokens with X.509 certificates.

This would provide a seamless and highly secure login mechanism for the client, reducing reliance on web-based authentication while aligning with hardware-backed security policies.

Describe alternatives you've considered
Custom Scripts: Employing custom scripts to integrate hardware keys indirectly, but this approach lacks native support and requires significant technical knowledge.
Relying on Web SSO: While feasible, web-based authentication does not utilize the potential of hardware security modules, especially in high-security environments.

Additional context
Supporting hardware keys for authentication would align the Netbird client with modern security practices and enhance its usability in enterprise settings. Many security-focused solutions already include such support, and adding this feature would make Netbird a more competitive and secure choice for networking needs.

If needed, I am happy to provide more details or test the feature with various hardware keys and smartcards.

Originally created by @TKaluza on GitHub (Nov 20, 2024). **Is your feature request related to a problem? Please describe.** Currently, the Netbird client supports login via website and SSO, which is efficient for administration. However, for the actual client network connection functionality, it lacks support for direct hardware-based authentication methods. This can be a limitation in environments that prioritize physical security measures or use Public Key Infrastructure (PKI) for enhanced access control. Users who rely on hardware keys or PKI cards, such as YubiKeys, Nitrokeys, or smartcards, may find the existing process inconvenient or not aligned with their security protocols. **Describe the solution you'd like** I would like the Netbird client to "natively" (or as good as possible 😉 ) support hardware-based authentication methods, allowing users to authenticate directly using devices like FIDO2 keys (YubiKey, Nitrokey) or PKI-enabled smart cards. This feature should be an alternative or addition for the functionality of the "Setup-Keys": - Authentication for connecting: Using the hardware device for login, with an optional PIN requirement for additional security. - Compatibility: Support for a range of devices, including USB, NFC, and Bluetooth-enabled keys, as well as PKI tokens with X.509 certificates. This would provide a seamless and highly secure login mechanism for the client, reducing reliance on web-based authentication while aligning with hardware-backed security policies. **Describe alternatives you've considered** Custom Scripts: Employing custom scripts to integrate hardware keys indirectly, but this approach lacks native support and requires significant technical knowledge. Relying on Web SSO: While feasible, web-based authentication does not utilize the potential of hardware security modules, especially in high-security environments. **Additional context** Supporting hardware keys for authentication would align the Netbird client with modern security practices and enhance its usability in enterprise settings. Many security-focused solutions already include such support, and adding this feature would make Netbird a more competitive and secure choice for networking needs. If needed, I am happy to provide more details or test the feature with various hardware keys and smartcards.
saavagebueno added the feature-requestsecuritysecurity-related labels 2025-11-20 05:30:15 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label feature-request security security-related
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1432
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?