FFFF Kerberos fallback to next provider (user federation) when · Issue #9290 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

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

Closed as not planned

Description

@Mystikal57

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.

Activity

  1. added
    area/ldapLDAP/Active Directory federation — user sync, group/attribute mapping
    kind/bugCategorizes a PR related to a bug
    on Dec 22, 2021
  2. added
    kind/featureCategorizes a PR related to a new feature
    and removed
    kind/bugCategorizes a PR related to a bug
    on Aug 11, 2022
  3. mposolda commented on Aug 11, 2022

    @mposolda
    Contributor

    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).

  4. hmlnarik commented on Feb 17, 2023

    @hmlnarik
    Contributor

    Closing this as duplicate of #14665

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/ldapLDAP/Active Directory federation — user sync, group/attribute mappingkind/featureCategorizes a PR related to a new feature

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0