Link OIDC users to Headscale users via providerId#479
Open
Link OIDC users to Headscale users via providerId#479
Conversation
drifterza
force-pushed
the
fix/issue-387-oidc-reconciliation
branch
4 times, most recently
from
54c3717 to
1d502bb
Compare
drifterza
force-pushed
the
fix/issue-387-oidc-reconciliation
branch
from
1d502bb to
b4a99cd
Compare
This was referenced Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #387
When
oidc.integrate_headscaleis enabled, Headplane matches the OIDC subject to Headscale users by extracting the subject from theirproviderIdfield (format:oidc/subject123). The matched Headscale user ID is stored in the database for future permission assignment.Changes:
headscale_user_idcolumn to users table via migrationintegrate_headscaleconfig option under oidc sectionAPI key authentication continues to work without onboarding (handled by existing shell loader check).
This PR handles the backend OIDC linking. See #481 for the complementary onboarding UI changes.