EPIC Goal

The goal of this epic is to provide a method to allow users to dynamically define custom user/group transformers for the keycloak-backend.

Background/Feature Origin

We need to provide a method for administrators/platform engineers to customize the keycloak-backend entity provider to create custom user/group entity mappings for ingested keycloak users/groups.

Why is this important?

Currently end users can only use the default transformers for keycloak users/groups, which would work for default keycloak setups. However, the default transformers might not for custom setups such as as setups utilizing external identity providers.

User Scenarios

If user uses keycloak with an external identity provider such as Google, the `username` field is an email (local@mail.domain) which contains disallowed characters. This would result in the entities not being ingested into the catalog.

Providing the user the ability to custom how the entities are generated from the IDPs would help resolve these issues.

Dependencies (internal and external)

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>