Expose krbPrincipalName as REMOTE_USER_PRINCIPAL#401
Merged
Fryguy merged 1 commit intoManageIQ:masterfrom Feb 18, 2026
Merged
Conversation
If it's available, we can expose the principal name as that gives a more consistent user lookup as sssd allows logins with email address or the freeipa/identity provider's username, leading to the username being not reliable for creating our internal user record based on it. This change is needed to support this: ManageIQ/manageiq#23723
Member
|
Checked commit jrafanie@b1ca3b2 with ruby 3.3.10, rubocop 1.56.3, haml-lint 0.69.0, and yamllint |
jrafanie
added a commit
to jrafanie/manageiq-appliance_console
that referenced
this pull request
Feb 13, 2026
jrafanie
added a commit
to jrafanie/manageiq-appliance_console
that referenced
this pull request
Feb 13, 2026
The principal name provides a consistent username for creating user records since sssd supports logins with email or the username from the authentication system (freeipa). Using this consistent principal name prevents creating duplicate users created from both the free ipa username and from the configured email address. Related: ManageIQ/manageiq#23723 ManageIQ/manageiq-appliance#401
This was referenced Feb 13, 2026
jrafanie
added a commit
to jrafanie/manageiq-appliance_console
that referenced
this pull request
Feb 13, 2026
The principal name provides a consistent username for creating user records since sssd supports logins with email or the username from the authentication system (freeipa). Using this consistent principal name prevents creating duplicate users created from both the free ipa username and from the configured email address. Related: ManageIQ/manageiq#23723 ManageIQ/manageiq-appliance#401
jrafanie
added a commit
to jrafanie/manageiq-appliance_console
that referenced
this pull request
Feb 13, 2026
The principal name provides a consistent username for creating user records since sssd supports logins with email or the username from the authentication system (freeipa). Using this consistent principal name prevents creating duplicate users created from both the free ipa username and from the configured email address. Related: ManageIQ/manageiq#23723 ManageIQ/manageiq-appliance#401
Fryguy
approved these changes
Feb 18, 2026
jrafanie
added a commit
to jrafanie/guides
that referenced
this pull request
Feb 19, 2026
jrafanie
added a commit
to jrafanie/manageiq-pods
that referenced
this pull request
Feb 19, 2026
We only set this for usage through sssd and httpd but this could be used as the de facto standard for all httpd based identity providers. Follow up to: ManageIQ/manageiq#23723 ManageIQ/manageiq-appliance#401 ManageIQ/guides#587
jrafanie
deleted the
expose-krbPrincipalName-as-REMOTE_USER_PRINCIPAL
branch
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
3 participants
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.
If it's available, we can expose the principal name as that gives a more consistent user lookup as sssd allows logins with email address or the freeipa/identity provider's username, leading to the username being not reliable for creating our internal user record based on it.
This change is needed to support this:
ManageIQ/manageiq#23723