-
Notifications
You must be signed in to change notification settings - Fork 11
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
Resource type: openid_user_realm_role_protocol_mapper #160
Comments
I managed to find an example in the documentation. Apparently it's a generic protocol mapper which we have to configure to cover different usecases: apiVersion: client.keycloak.crossplane.io/v1alpha1
kind: ProtocolMapper
metadata:
name: openid-role-mapper
spec:
forProvider:
clientId: another-openid-client
config:
claim.name: roles
multivalued: "true"
name: role-mapper
protocol: openid-connect
protocolMapper: oidc-usermodel-realm-role-mapper
realmId: another-realm
providerConfigRef:
name: keycloak-provider-config
|
Hey man, sorry for the radio silence, i'm in the process of moving to a different location. |
No worries! Apparently I didn't read the docs carefully enough so that's on me
I'm not entirely sure that's necessary. There is currently a way to achieve the same result and it is in fact documented. I wouldn't say this is a high priority item on the to-do list |
I am working on converting some Terraform manifests over to crossplane. I have a resource of this type:
https://registry.terraform.io/providers/mrparkers/keycloak/latest/docs/resources/openid_user_realm_role_protocol_mapper
I did not manage to find it while looking through the docs. Is it not supported?
The text was updated successfully, but these errors were encountered: