Ensure that the EncryptedKey is passed to the DecryptionKeyLocator for SAML - #23203
Conversation
Passing run #8994 ↗︎Details:
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
|||||||||||||||
There was a problem hiding this comment.
We recently made some changes to the way labels are handled, so the namespace can now be omitted.
| fieldLabelId="identity-provider:encryptionAlgorithm" | |
| fieldLabelId="encryptionAlgorithm" |
There was a problem hiding this comment.
@jonkoops I had just moved it! 😄 Done now!
But one question, modifying this I saw that the help message was not OK. I needed to also change the helpText={th("encryptionAlgorithmHelp")} (adding suffix Help) in the HelpItem. I see all the HelpItem (at least in the saml provider) are not showing the proper help message. I just modified the one that I was moving.
There was a problem hiding this comment.
Could you log a separate issue for that one? I think this might be because of the recent changes made to the labels. ping @edewit
There was a problem hiding this comment.
Created: #23255 (It just happens in main, not in 22.0.3.)
3ba623a to
75c76f5
Compare
Unreported flaky test detectedIf the below flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.webauthn.AppInitiatedActionWebAuthnTest#proceedSetupWebAuthnLogoutOtherSessionsCheckedKeycloak CI - WebAuthn IT (chrome) |
ghost
left a comment
There was a problem hiding this comment.
Unreported flaky test detected, please review
75c76f5 to
60e0e63
Compare
|
I give up today, something is failing today. Tomorrow I will rebase and try again. |
ghost
left a comment
There was a problem hiding this comment.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the below flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.ui.account2.DeleteAccountTest#navigationTestKeycloak CI - Account Console IT (firefox) |
60e0e63 to
6d1114c
Compare
ghost
left a comment
There was a problem hiding this comment.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the below flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.x509.X509BrowserCRLTest#loginSuccessWithCRLSignedWithIntermediateCA3FromTruststoreKeycloak CI - FIPS IT (non-strict) |
ghost
left a comment
There was a problem hiding this comment.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the below flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.x509.X509BrowserCRLTest#loginSuccessWithCRLSignedWithIntermediateCA3FromTruststoreKeycloak CI - FIPS IT (non-strict) |
This should be fixed now, could you rebase your PR on |
6d1114c to
1a26027
Compare
|
OK! All CI passed now. Thanks @jonkoops! @pedroigor ready to merge now if you don't see anything more. |
mposolda
left a comment
There was a problem hiding this comment.
@rmartinc @jonkoops @pedroigor Thanks everyone for the work on this and the review
Closes #22974
Two little issues in SAML decryption of elements:
EncyptedKeysometimes is outside theEncryptedData(next sibling). And it was not passed to theSAMLDecryptionKeysLocator. So the locator couldn't filter by the encryption alg set in the response. This threw a NPE iterating the keys. Code also changed to not decode theEncyptedKeytwice (if it was already inside the data) and to avoid keys without private key.wantAuthnRequestsSignedis ON. That makes no sense, the encryption alg is only used to force the alg in decrypting the received elements, not when we sign the requests. I have moved it to show/hide whenwantAssertionsEncryptedis ON. (I think that there is no lint or test errors, but I'm never sure. 😄 )The combination of the two problems threw the NPE in the related issue. The alg was not forced (because the box was hidden and the user didn't see how to force it) and then the
EncryptedKeywas outside theEncrypedDatain okta. Test added to modify the XML and be similar to the one produced by okta.