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

[Feature Request] Add SAML Authentication Support for NetBird #1597

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

Originally created by @chirag-rastogi on GitHub (Feb 6, 2025).

Description:
NetBird currently supports OIDC for authentication, which is beneficial. However, SAML ( support is still essential for many organizations that rely on enterprise SSO solutions which might not allow OIDC.

Why SAML is Needed Despite OIDC Support:
While OIDC is modern and widely used, many enterprises still operate primarily on SAML due to:

  • Existing Enterprise Infrastructure: Many organizations have legacy and compliance-driven IdPs that only support SAML.
  • SSO Standardization: Some organizations prefer a unified authentication method across all applications, and SAML remains a standard in many enterprises.
  • Seamless Integration with Large IdPs: Many IdPs offer stronger native SAML support over OIDC, making integration simpler for IT teams.

Proposed Implementation:

  • Add SAML authentication alongside the existing OIDC integration.
  • Provide SP metadata for easy integration with IdPs.
  • Enable role-based access control (RBAC) mapping via SAML attributes.
  • Ensure compatibility with major SAML providers (Google Workspace, Okta, Microsoft Entra ID, OneLogin).

Alternative Workarounds:
While SAML-to-OIDC bridges exist, they add unnecessary complexity and overhead. Native SAML support would streamline deployment and improve security

Originally created by @chirag-rastogi on GitHub (Feb 6, 2025). Description: NetBird currently supports OIDC for authentication, which is beneficial. However, SAML ( support is still essential for many organizations that rely on enterprise SSO solutions which might not allow OIDC. Why SAML is Needed Despite OIDC Support: While OIDC is modern and widely used, many enterprises still operate primarily on SAML due to: - **Existing Enterprise Infrastructure:** Many organizations have legacy and compliance-driven IdPs that only support SAML. - **SSO Standardization:** Some organizations prefer a unified authentication method across all applications, and SAML remains a standard in many enterprises. - **Seamless Integration with Large IdPs:** Many IdPs offer stronger native SAML support over OIDC, making integration simpler for IT teams. Proposed Implementation: - Add SAML authentication alongside the existing OIDC integration. - Provide SP metadata for easy integration with IdPs. - Enable role-based access control (RBAC) mapping via SAML attributes. - Ensure compatibility with major SAML providers (Google Workspace, Okta, Microsoft Entra ID, OneLogin). Alternative Workarounds: While SAML-to-OIDC bridges exist, they add unnecessary complexity and overhead. Native SAML support would streamline deployment and improve security
saavagebueno added the feature-request label 2025-11-20 05:33:31 -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
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#1597
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?