KEYCLOAK-19519 Encryption algorithm RSA-OAEP with A256GCM#8553
Conversation
46c3091 to
1ee18f7
Compare
a9a123b to
655dce5
Compare
|
@tnorimat do you have a question about this? |
|
@fbrissi Hello, It seems that this PR lacks the integration tests. |
|
@fbrissi In #8708, I've done the same thing for generated key as this PR does for imported key. I've proposed two options in #8708 (comment) and taken the option 1. It seems that this PR may take the option 2. Could you consider the option 1? Namely providing ImportedRsaKey for use = sig and ImportedRsaKey for use = enc. @mposolda what do you think about it? |
|
Right, thanks guys. |
8bf7341 to
7948d8d
Compare
|
Hey guys, I made the suggested changes |
7948d8d to
085e69e
Compare
085e69e to
cfd0148
Compare
cfd0148 to
55e5268
Compare
|
@mposolda Could you check this PR? |
mposolda
left a comment
There was a problem hiding this comment.
@fbrissi Thanks for the PR!
@tnorimat Thanks for the review! I am approving mostly based on your review since you are most familiar with this codebase due your recent work on this.
Before merging this, I am trying to rerun the GH actions. Also it will be needed to create GH issue instead of JIRA and add this issue to the commit message (Although I can add it when I am merging PR as I can change commit message and attach GH issue to it. So no need to update PR and change commit message just because of this).
Based on #8243
Jira issue KEYCLOAK-19519