Some OAuth2 services may consume custom claims from an id token for access control or other
policy decisions. Each custom claim is a key:values set, where there can be many values
associated to a claim name. Different applications may expect these values to be formatted
(joined) in different ways.
The KanidmOAuth2Client custom resource definition (CRD) defines an OAuth2 client integration in
Kanidm. This resource allows you to configure OAuth2 clients that can interact with the Kanidm
authorization server. The CRD supports various configurations, including scope maps,
claim maps, and other OAuth2 client settings.
More info:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
Most recent observed status of the Kanidm Group. Read-only.
More info:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
Aliases for canonical secret keys.
Allows specifying additional key names for CLIENT_ID and CLIENT_SECRET values.
Duplicate aliases are deduplicated. Invalid key names are rejected by the webhook.