8000 Do not assign CURRENT_AUTHENTICATION_EXECUTION on fork (26.6) by rmartinc · Pull Request #55025 · keycloak/keycloak · GitHub
[go: up one dir, main page]
Skip to content

Do not assign CURRENT_AUTHENTICATION_EXECUTION on fork (26.6) #55025

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ahus1 merged 1 commit into from
Nov 12, 2026
Merged

Do not assign CURRENT_AUTHENTICATION_EXECUTION on fork (26.6) #55025

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion services/src/main/java/org/keycloak/authentication/DefaultAuthenticationFlow.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -526,7 +526,6 @@ public Response processResult(AuthenticationProcessor.Result result, boolean isA
throw new AuthenticationFlowException(result.getError(), result.getEventDetails(), result.getUserErrorMessage());
case FORK:
logger.debugv("reset browser login from authenticator: {0}", execution.getAuthenticator());
processor.getAuthenticationSession().setAuthNote(AuthenticationProcessor.CURRENT_AUTHENTICATION_EXECUTION, execution.getId());
throw new ForkFlowException(result.getSuccessMessage(), result.getErrorMessage());
case FORCE_CHALLENGE:
case CHALLENGE:
Expand Down
Loading
0