Skip to content
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.

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

Do not add authenticators directly to authentication flows but use a conditional sub-flow #29446

Closed
pedroigor opened this issue May 10, 2024 · 0 comments · Fixed by #29785
Closed
Assignees

Comments

@pedroigor
Copy link
Contributor

pedroigor commented May 10, 2024

Today, authentication execution steps are added directly to the authentication flow.

While this works fine for what we need so far, it is not the ideal and we want to group those executions within a conditional sub-flow instead.

The main argument for having this is the possibility to add or change the sub-flow without changing the authentication flow itself so that we have more flexibility to change how organization members authenticate to a realm.

@pedroigor pedroigor assigned pedroigor and sguilhen and unassigned pedroigor May 13, 2024
sguilhen added a commit to sguilhen/keycloak that referenced this issue May 22, 2024
…ult browser and first broker login flows

Closes keycloak#29446

Signed-off-by: Stefan Guilhen <sguilhen@redhat.com>
sguilhen added a commit to sguilhen/keycloak that referenced this issue May 22, 2024
…ult browser and first broker login flows

Closes keycloak#29446

Signed-off-by: Stefan Guilhen <sguilhen@redhat.com>
pedroigor pushed a commit that referenced this issue May 22, 2024
…ult browser and first broker login flows

Closes #29446

Signed-off-by: Stefan Guilhen <sguilhen@redhat.com>
tmorin pushed a commit to tmorin/keycloak that referenced this issue May 23, 2024
…ult browser and first broker login flows

Closes keycloak#29446

Signed-off-by: Stefan Guilhen <sguilhen@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants