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

Support multiple user configurations on a shared machine #862

New Issue
Open
opened 2025-11-20 05:18:51 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:18:51 -05:00
Owner
Copy Link

Originally created by @Francois-YACOB on GitHub (May 9, 2024).

Context :

  • Netbird create an overlay network that contains peers
  • peers have groups : from manual assignment, from auto-assigned by setup keys, from user group propagations, etc...
  • groups are used to defined access policies

This is perfect from a network architecture perspective... and all of these settings are peer-centric, the groups are assigned to the peer and when the user connects the VPN through the IDP, there is no information used from the user.

Missing use case :

  • in the scenario of shared computer, it makes sense that one user connects to the VPN and have some access policies based on its groups to be added to the peers.
  • this user disconnects and another user login, the peer should now have different access policies if 2nd user have different groups.

Request for this feature :

  • at SSO Login time, the groups at the user level is added to the peer, thus gives additional flexibility for access policies
  • when user disconnects from the Netbird UI (or after login expiration), additional groups are removed from the peers

Objective :

  • allowing some dynamic user-centrics groups policy makes Netbird more competitive to traditional VPN solution that are user profile centrics.
  • from an architectural perspective, Netbird with peer-centric access policy is comparable to IPSEC site-to-site
  • adding user group access policy will lead Netbird to be comparable to IPSEC/IKEV2 roadwarrior configuration and globally to compete with OpenVPN/Pritunl and other vendor VPN (Cisco connect, Sophos VPN)
Originally created by @Francois-YACOB on GitHub (May 9, 2024). Context : - Netbird create an overlay network that contains peers - peers have groups : from manual assignment, from auto-assigned by setup keys, from user group propagations, etc... - groups are used to defined access policies This is perfect from a network architecture perspective... and all of these settings are peer-centric, the groups are assigned to the peer and when the user connects the VPN through the IDP, there is no information used from the user. Missing use case : - in the scenario of shared computer, it makes sense that one user connects to the VPN and have some access policies based on its groups to be added to the peers. - this user disconnects and another user login, the peer should now have different access policies if 2nd user have different groups. Request for this feature : - at SSO Login time, the groups at the user level is added to the peer, thus gives additional flexibility for access policies - when user disconnects from the Netbird UI (or after login expiration), additional groups are removed from the peers Objective : - allowing some dynamic user-centrics groups policy makes Netbird more competitive to traditional VPN solution that are user profile centrics. - from an architectural perspective, Netbird with peer-centric access policy is comparable to IPSEC site-to-site - adding user group access policy will lead Netbird to be comparable to IPSEC/IKEV2 roadwarrior configuration and globally to compete with OpenVPN/Pritunl and other vendor VPN (Cisco connect, Sophos VPN)
saavagebueno added the feature-request label 2025-11-20 05:18:51 -05:00
saavagebueno commented 2025-11-20 05:18:52 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 23, 2025):

The missing use case will be covered by https://github.com/netbirdio/netbird/issues/3273

@nazarewk commented on GitHub (Apr 23, 2025): The missing use case will be covered by https://github.com/netbirdio/netbird/issues/3273
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#862
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?