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

OpenId and SAML Client's attributes #389

Closed
wants to merge 75 commits into from

Conversation

slavko-vega
Copy link

Supported are attributes for OpenId and SAML clients

slavko-vega and others added 30 commits May 13, 2020 09:12
…ric-client-role-mapper-extension

Extension of keycloak_generic_client_role_mapper resource to support realm-level roles association
…reference

Features/management permission reference
Features/identity-provider-mapper-extra-config
…loak-generic-client-role-mapper-extension

Revert "Extension of keycloak_generic_client_role_mapper resource to support realm-level roles association"
…urce to support realm-level roles association""

This reverts commit bae0f66.
…ric-client-role-mapper-extension

keycloak_generic_client_role_mapper realm-level roles association support
@mrparkers
Copy link
Owner

I guess I'm not completely understanding the problem we're trying to solve here. I understand that your goal is to add user-defined attributes to API calls for resources such as openid and saml clients, but is there any reason that we need to use reflection or define reserved keys?

My thinking is that we could just allow users to use this attributes map to define any properties they want on the model that is sent to the Keycloak API, and it's up to them to make sure that they aren't overwriting other attributes or sending attributes that the Keycloak API will reject. As long as we know what field we're trying to add, we know what field to look for in the response we get back so the state can be updated accordingly.

This appears to be what we're doing with the IdentityProviderMapperConfig, right? Can we take the same approach for openid and saml clients as well?

@slavko-vega
Copy link
Author

slavko-vega commented Nov 1, 2020

Hey @mrparkers , you're totally right. I wasn't aware of that implementation in IdentityProviderMapperConfig. I'll use the same approach for OpenId/SAML client.

@slavko-vega
Copy link
Author

Hi @mrparkers, client (OpenId and SAML) attributes are implemented as extra_config.

@civ0
Copy link

civ0 commented Feb 16, 2021

Hi all, are there any updates on this PR?

Setting custom attributes on clients would be very useful for me. Please let me know, if there is something I can do to help progressing this PR.

@Tokynet
Copy link

Tokynet commented Jul 1, 2022

BUMP @slavko-vega and @mrparkers

@mrparkers
Copy link
Owner

Hi everyone, I think the functionality that's been introduced within this PR has already been implemented via several other PRs:

Let me know if you think that anything else is missing, but I think for now we can close this PR.

@mrparkers mrparkers closed this Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants