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

Kerberos fallback to next provider (user federation) when #9290

Closed
Mystikal57 opened this issue Dec 21, 2021 · 2 comments
Closed

Kerberos fallback to next provider (user federation) when #9290

Mystikal57 opened this issue Dec 21, 2021 · 2 comments
Labels
area/ldap kind/feature Categorizes a PR related to a new feature

Comments

@Mystikal57
Copy link

Mystikal57 commented Dec 21, 2021

Describe the bug

hi,

Why keycloak/kerberos doesn't fallback to next federation provider when it doesn't find user in the first federation provider ?

Kerberos/SPNEGO authentication succeeded with username [user1], but couldn't find or create user with federation provider [fed01]

thank you

Version

15.1

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Anything else?

There is support ticket 286 asking for this.

@stianst stianst added area/ldap kind/bug Categorizes a PR related to a bug status/triage labels Dec 22, 2021
@mposolda mposolda added kind/feature Categorizes a PR related to a new feature and removed kind/bug Categorizes a PR related to a bug labels Aug 11, 2022
@mposolda
Copy link
Contributor

mposolda commented Aug 11, 2022

I am changing to task as support for the fallback is rather a new thing to implement than a bug.

There are support tickets related to this (See Anything Else section).

@hmlnarik
Copy link
Contributor

Closing this as duplicate of #14665

@hmlnarik hmlnarik closed this as not planned Won't fix, can't repro, duplicate, stale Feb 17, 2023
@ghost ghost removed the status/triage label Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ldap kind/feature Categorizes a PR related to a new feature
Projects
None yet
Development

No branches or pull requests

4 participants