[GH-ISSUE #5103] Force User Authentication Against NetBird by Administrator #10714

Open
opened 2026-08-05 01:27:01 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @shayanprakashkannur on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5103

Is your feature request related to a problem? Please describe.

Currently, administrators have no way to force user authentication after making changes to NetBird (such as upgrading to a new version or modifying authentication settings). This creates uncertainty about whether the authentication flow works correctly before rolling out updates to all end users, which can lead to potential disruptions or security gaps.

Describe the solution you'd like

Introduce a feature that allows administrators to trigger user authentication manually for selected users or groups. This could be implemented via the admin dashboard. The goal is to validate that authentication mechanisms (SSO, identity provider integration, etc.) are functioning correctly before deploying updates to production environments.

Describe alternatives you've considered

No alternatives found, only way to get the results now is when any of the user who completes the authentication cycle (once in 7 days) and authenticates again finds any issues.

Additional context

This feature would help administrators confidently push updates without risking authentication failures for end users. It would also improve security and reliability by ensuring authentication changes are verified proactively.
Possible implementation ideas:

-- Admin Dashboard Control: A button or action to trigger re-authentication for specific users.

Originally created by @shayanprakashkannur on GitHub (Jan 14, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5103 **Is your feature request related to a problem? Please describe.** Currently, administrators have no way to force user authentication after making changes to NetBird (such as upgrading to a new version or modifying authentication settings). This creates uncertainty about whether the authentication flow works correctly before rolling out updates to all end users, which can lead to potential disruptions or security gaps. **Describe the solution you'd like** Introduce a feature that allows administrators to trigger user authentication manually for selected users or groups. This could be implemented via the admin dashboard. The goal is to validate that authentication mechanisms (SSO, identity provider integration, etc.) are functioning correctly before deploying updates to production environments. **Describe alternatives you've considered** No alternatives found, only way to get the results now is when any of the user who completes the authentication cycle (once in 7 days) and authenticates again finds any issues. **Additional context** This feature would help administrators confidently push updates without risking authentication failures for end users. It would also improve security and reliability by ensuring authentication changes are verified proactively. Possible implementation ideas: -- Admin Dashboard Control: A button or action to trigger re-authentication for specific users.
saavagebueno added the feature-request label 2026-08-05 01:27:01 -04:00
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10714