Repository navigation
Infinispan Protostream Marshaller - #29474
Conversation
81b9388 to
81f1ba0
Compare
There was a problem hiding this comment.
@pruivo Do you plan to add the proto compatibility check capabilities as part of this PR or should we create an issue to add that in a subsequent PR? I would be happy with the latter given how large the current PR is.
81f1ba0 to
70caa5f
Compare
8e8b859 to
25c5cb1
Compare
|
Please do not merge until we decide if this should be included in Keycloak 25, or shortly after the release |
25c5cb1 to
d3bf888
Compare
d3bf888 to
b716502
Compare
Unreported flaky test detectedIf the 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.broker.KcOidcBrokerTest#testPostBrokerLoginFlowWithOTP_bruteForceEnabledKeycloak CI - Java Distribution IT (windows-latest - temurin - 19) |
b716502 to
c91033c
Compare
|
Rebased and added documentation to
|
Unreported flaky test detectedIf the 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.oauth.TokenIntrospectionTest#testUnsupportedTokenorg.keycloak.testsuite.broker.KcOidcBrokerTest#testPostBrokerLoginFlowWithOTP_bruteForceEnabledKeycloak CI - Java Distribution IT (ubuntu-latest - temurin - 17) org.keycloak.testsuite.oauth.TokenIntrospectionTest#testUnsupportedToken |
c91033c to
8d26723
Compare
Unreported flaky test detectedIf the 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.broker.KcOidcBrokerTest#testPostBrokerLoginFlowWithOTP_bruteForceEnabledKeycloak CI - Java Distribution IT (windows-latest - temurin - 17) |
ac26393 to
8e8a6f7
Compare
There was a problem hiding this comment.
Thank you for the PR! Found a typo in the include for the release notes. Used the opportunity to remove some now unused code in the PersitentUserSessionProvider.
I didn't remove that method because of the javadoc: Isn't useful anymore? |
b5d3a88 to
d2a1573
Compare
With the change of the serialization format, it IMHO became less useful. But ok, let's keep it for now. I realize I only deleted half of it anyway :-( |
Head branch was pushed to by a user without write access
b9788fc to
652cb51
Compare
There was a problem hiding this comment.
Great work @pruivo, just a few minor things I have noticed so far.
There was a problem hiding this comment.
None of the IDs defined above are used anywhere in the code according to Intellij.
There was a problem hiding this comment.
The modules where they are used do not depend on this one. The comments tell where they are used.
Head branch was pushed to by a user without write access
|
Added a new commit with @ryanemerson suggestions 👍 |
16846bd to
ed400fe
Compare
Closes keycloak#29394 Signed-off-by: Pedro Ruivo <pruivo@redhat.com> Co-authored-by: Alexander Schwartz <aschwart@redhat.com>
3218aff to
25e3dfd
Compare
|
Rebased and squashed the commits. I suspect that I changed how the migration works and moved the code to |
Closes #29394
I'm gathering earlier feedback and sharing how it will end up.
Pending tasks are:
Out of scope: Existing entries in the session cache will be migrated in PR #29377
Migration
The migration path is under discussion and has the following assumptions:
The most appealing solution is to start a separate, non-clustered Infinispan
CacheManagerwith JBoss-Marshalling configured (theCacheManageris limited to a single marshalled). ThisCacheManagerwill be used to read the old session data. Then, we have the following 2 scenariosCacheManagerto read the sessions and store them in the database. The cache is clear at the end.CacheManagerand writes them in the Protostream enabledCacheManager.