You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ui: login session checked before proceding. - #14586
This PR checks the session key before assuming the login was successful.
It also checks whether config.json load failed or some other error occurred after loading.
... and ...
When an authenticator throws an unexpected exception during login, ApiServlet
swallowed it and answered 200 with an empty body, which the UI took for a login
without a session key. Such an exception is now answered with a 500 error
instead of an empty response, and the session is invalidated when it happens
during login, so no authenticated session is left behind.
The NPE that triggered this for first LDAP logins (#14528) has meanwhile been
fixed in DefaultLoginAPIAuthenticatorCmd by #14098; this PR was rebased on
top of that and no longer touches that class.
@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress.
The reason will be displayed to describe this comment to others. Learn more.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
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
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.
Description
This PR checks the session key before assuming the login was successful.
It also checks whether config.json load failed or some other error occurred after loading.
... and ...
When an authenticator throws an unexpected exception during login, ApiServlet
swallowed it and answered 200 with an empty body, which the UI took for a login
without a session key. Such an exception is now answered with a 500 error
instead of an empty response, and the session is invalidated when it happens
during login, so no authenticated session is left behind.
The NPE that triggered this for first LDAP logins (#14528) has meanwhile been
fixed in
DefaultLoginAPIAuthenticatorCmdby #14098; this PR was rebased ontop of that and no longer touches that class.
Fixes: #14528
Co-Authored-By: Claude Opus 5.5 [email protected]
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?