-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
improvements to the keycloak_realm_key module #7698
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution!
changelogs/fragments/7698-improvements-to-keycloak_realm_key.yml
Outdated
Show resolved
Hide resolved
changelogs/fragments/7698-improvements-to-keycloak_realm_key.yml
Outdated
Show resolved
Hide resolved
My pleasure. I made the suggested code changes, thanks for putting the time in to review this PR. |
If I may (not a maintainer, merely a user of the collection) - I would propose to cover the whole set of supported algorithms by tests. And thanks for contribution, we were going to implement this addition ourselves in the following months as well. |
There is also some other functionality I have working but did not include in this PR, which involves managing the generated keys (for example the |
Some feedback from the module maintainers would be nice. In general the change looks OK to me, except that |
"PS512", | ||
"RSA1_5", | ||
"RSA-OAEP", | ||
"RSA-OAEP-256", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding these makes sense. I only had a need for RS256 and I did not want to overreach. However, I think adding one integration test per algorithm would be useful as the list of supported algorithms might change over time. Or these might be a typo in there 😄.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea I can add some basic integration tasks to check these I guess, although some algorithms belong on certain key types only. For example, you would not want to attempt to set RSA-OAEP
on your signing key. I was hoping that the end user of this module would understand the values they are setting so that we don't have to write too much validation code. Ideally the keycloak api will return an error in these cases so we can just pass that error on. I think maybe we should tackle this in another PR though...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. If nobody objects, I'll merge this in ~a week.
Backport to stable-8: 💚 backport PR created✅ Backport PR branch: Backported as #7768 🤖 @patchback |
* add support for rsa enc key usage, more algorithms, and make certficate optional * fix formatting * adding changelog fragment * made suggested code changes based on review * fix typo and be more clear * revert certificate to previous defined settings (cherry picked from commit 702dd9b)
…ealm_key module (#7768) improvements to the keycloak_realm_key module (#7698) * add support for rsa enc key usage, more algorithms, and make certficate optional * fix formatting * adding changelog fragment * made suggested code changes based on review * fix typo and be more clear * revert certificate to previous defined settings (cherry picked from commit 702dd9b) Co-authored-by: George Bolo <george.bolo@gmail.com>
SUMMARY
This PR makes the following improvements to the
keycloak_realm_key
module:rsa-enc
no_log
for certificate since this is not sensitive informationISSUE TYPE
COMPONENT NAME
module:
keycloak_realm_key
ADDITIONAL INFORMATION
Tested against Keycloak
v22.0.4
API.