Upgrading notes for user profile
closes #24491 Signed-off-by: mposolda <mposolda@gmail.com> Co-authored-by: andymunro <48995441+andymunro@users.noreply.github.com>
This commit is contained in:
parent
0c6ed85579
commit
4ec85707f4
2 changed files with 11 additions and 1 deletions
|
@ -57,5 +57,6 @@ paginated lookup of subgroups. Thanks to https://github.com/alice-wondered[Alice
|
|||
|
||||
Declarative user profile is still a preview feature in this release, but we are working hard on promoting it to a supported feature. Feedback is welcome.
|
||||
If you find any issues or have any improvements in mind, you are welcome to create https://github.com/keycloak/keycloak/issues/new/choose[Github issue],
|
||||
ideally with label `area/user-profile`.
|
||||
ideally with the label `area/user-profile`. It is also recommended to check the link:{upgradingguide_link}[{upgradingguide_name}] with the migration changes for this
|
||||
release for some additional informations related to the migration.
|
||||
|
||||
|
|
|
@ -145,3 +145,12 @@ The endpoint `POST {keycloak server}/realms/{realm}/partial-export` and the corr
|
|||
= Removal of the options to trim the event's details length
|
||||
|
||||
Since this release, Keycloak supports long value for `EventEntity` details column. Therefore, it no longer supports options for trimming event detail length `--spi-events-store-jpa-max-detail-length` and `--spi-events-store-jpa-max-field-length`.
|
||||
|
||||
= User Profile updates
|
||||
|
||||
This release includes many fixes and updates that are related to user profile as we are working on promoting this feature from preview to officially supported.
|
||||
Minor changes exist for the SPI such as the newly added method `boolean isEnabled(RealmModel realm)` on `UserProfileProvider` interface. Also
|
||||
some user profile classes and some validator related classes (but not builtin validator implementations) were moved from `keycloak-server-spi-private` to
|
||||
`keycloak-server-spi` module. However, the packages for java classes remain the same. You might be affected in some corner cases, such as when you
|
||||
are overriding the built-in implementation with your own `UserProfileProvider` implementation However, note that `UserProfileProvider` is an unsupported SPI.
|
||||
|
||||
|
|
Loading…
Reference in a new issue