fix(auth): honor session-stored server selection in getAutoLoginServer()#93
Open
jcdelepine wants to merge 1 commit into
Open
fix(auth): honor session-stored server selection in getAutoLoginServer()#93jcdelepine wants to merge 1 commit into
jcdelepine wants to merge 1 commit into
Conversation
Companion to horde/base's login.php change: base now stores posted per-app login params (raw, ungrouped by meaning) in the session after a successful Horde-level login, regardless of which auth driver handled it. Read imp's own 'imp_server_key' field from there and prefer it over the existing preferred/first-backend fallback, so a server chosen on the login screen actually takes effect — even when Horde authenticated via LDAP/SQL rather than through imp itself.
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.
Companion to horde/base's login.php change: base now stores posted per-app login params (raw, ungrouped by meaning) in the session after a successful Horde-level login, regardless of which auth driver handled it.
Read imp's own 'imp_server_key' field from there and prefer it over the existing preferred/first-backend fallback, so a server chosen on the login screen actually takes effect — even when Horde authenticated via LDAP/SQL rather than through imp itself.