RANGER-5717: Disable SSO in docker, ensure readiness health check registers user in DB - #1158
Open
kumaab wants to merge 2 commits into
Open
RANGER-5717: Disable SSO in docker, ensure readiness health check registers user in DB#1158kumaab wants to merge 2 commits into
kumaab wants to merge 2 commits into
Conversation
ramackri
approved these changes
Aug 15, 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
2 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.
What changes were proposed in this pull request?
In docker env,
ranger.sso.enabled=truewas added in #1120.To ensure readiness healthcheck API registers the healthcheck user (
ranger.admin.healthcheck.username) in the DB, updateSessionMgr.javato allow user creation irrespective of config:ranger.sso.enabled.Setting
ranger.sso.enabled=falseto allow logout from Ranger UI to be functional.Note: When using header based authentication,
ranger.sso.enabledmust be set to true to allow any authenticated user to be created in Ranger DB.How was this patch tested?
Tested using both scenarios:
that the API endpoint is accessible via
ranger.admin.healthcheck.usernameuser and results in user creation in DB.