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

Update user attributes via API #2425

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

Originally created by @adsehgal on GitHub (Oct 29, 2025).

Using self hosted NB with self hosted Zitadel V4.x.x (API V2), I have a second Zitadel organization I use to allow external users onto my netbird network with cross-org grants. While these users are able to authenticate, etc, user data is not pulled into netbird, ie: user name, emails are not pulled in, only their user ID (from the IDP is):

Image the image shows 2 users from a granted zitadel org, and my user that is in the zitadel org where the netbird service user is allowed.

Now this is actually a problem that upgrading Netbird to support Zitadel API V2 will solve but in the meantime I propose the following:

Allow user attributes to be updated via the API such as user name, and email. Similar to how currently user auto-groupings and role can be updated.

Doing so would allow me to setup n8n automations to scan newly created users in Zitadel and sync and update their attributes (name and email) into netbird. This would allow my team to better manage users within the netbird dashboard.

For context:
In zitadel, I setup a netbird project under the organization "AGOC" where I also setup the netbird service user as recommended in the advanced self hosting guide. This allows all users in the AGOC org to authenticate with NB and all their user info shows just fine. To keep some isolation, any third party contractors are created under the zitadel organization "External Netbird Users", these users are able to authenticate just fine but since netbird is using API V1 of zitadel, the service user is unable to pull information of these external users, only their user ID

Originally created by @adsehgal on GitHub (Oct 29, 2025). Using self hosted NB with self hosted Zitadel V4.x.x (API V2), I have a second Zitadel organization I use to allow external users onto my netbird network with cross-org grants. While these users are able to authenticate, etc, user data is not pulled into netbird, ie: user name, emails are not pulled in, only their user ID (from the IDP is): <img width="726" height="214" alt="Image" src="https://github.com/user-attachments/assets/49fef2d0-57c0-47ac-b957-06799ff3aa15" /> the image shows 2 users from a granted zitadel org, and my user that is in the zitadel org where the netbird service user is allowed. Now this is actually a problem that upgrading Netbird to support Zitadel API V2 will solve but in the meantime I propose the following: Allow user attributes to be updated via the API such as user name, and email. Similar to how currently user auto-groupings and role can be updated. Doing so would allow me to setup n8n automations to scan newly created users in Zitadel and sync and update their attributes (name and email) into netbird. This would allow my team to better manage users within the netbird dashboard. For context: In zitadel, I setup a netbird project under the organization "AGOC" where I also setup the netbird service user as recommended in the advanced self hosting guide. This allows all users in the AGOC org to authenticate with NB and all their user info shows just fine. To keep some isolation, any third party contractors are created under the zitadel organization "External Netbird Users", these users are able to authenticate just fine but since netbird is using API V1 of zitadel, the service user is unable to pull information of these external users, only their user ID
saavagebueno added the feature-request label 2025-11-20 07:09:36 -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#2425
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?