8000 Do not assign CURRENT_AUTHENTICATION_EXECUTION on fork by rmartinc · Pull Request #54205 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Do not assign CURRENT_AUTHENTICATION_EXECUTION on fork - #54205

Merged
ahus1 merged 1 commit into
keycloak:mainfrom
rmartinc:issue-54176
Oct 21, 2026
Merged

ahus1 merged 1 commit into
keycloak:mainfrom
rmartinc:issue-54176

Conversation

@rmartinc
Copy link
Copy Markdown
Contributor

Closes #54176

Just not assigning the CURRENT_AUTHENTICATION_EXECUTION on fork. It's not needed and I prefer to not ste anything here.

8000
Closes keycloak#54176

Signed-off-by: rmartinc <rmartinc@redhat.com>
@rmartinc
rmartinc requested a review from a team as a code owner October 21, 2026 08:16
Copilot AI balanced review requested due to automatic review settings October 21, 2026 08:16
Copilot AI left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The isolated removal matches the issue requirements, with no blocking issues identified.

No open issues 🎉

What changed in this PR

Removes unnecessary authentication-execution tracking when a flow forks, addressing #54176.

Changes:

  • Stops setting CURRENT_AUTHENTICATION_EXECUTION in the FORK branch.
  • Leaves fork exception handling unchanged.
File Description
services/​src/​main/​java/​org/​keycloak/​authentication/​DefaultAuthenticationFlow.java Removes the execution-note assignment on fork.

Review effort: Balanced

@mabartos mabartos left a comment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, not needed for FORK, so let's remove it to be more safe.

@ahus1
ahus1 merged commit 3c07b87 into keycloak:main Oct 21, 2026
98 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Do not assign CURRENT_AUTHENTICATION_EXECUTION on fork

4 participants

0