External-Mirrors/keycloak
2
0
Fork 0
mirror of https://github.com/keycloak/keycloak.git synced 2026-01-10 15:32:05 -03:30
Code Issues Packages Projects Releases Wiki Activity

add index for user_id and type on event_entity

Browse Source 
Closes #26995

Signed-off-by: Oliver Cremerius <antikalk@users.noreply.github.com>
Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
Co-authored-by: Alexander Schwartz <aschwart@redhat.com>
This commit is contained in:
Oliver 2025-07-30 22:52:48 +02:00 committed by GitHub
parent 97dfbd2c84
commit 27cd19e68e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/documentation/upgrading/topics/changes/changes-26_4_0.adoc
View File

@ -65,6 +65,13 @@ The feature is enabled for a realm, if `Update Email` required action is enabled
The feature slightly changes behaviour from previous versions when updating the profile during the authentication flow (e.g. when running the `UPDATE_PROFILE` required action).
If an existing user does have an email set when updating the profile during the authentication flow, the email attribute will not be available.
=== New database index on the `EVENT_ENTITY` table
The table `EVENT_ENTITY` now has an index `IDX_EVENT_ENTITY_USER_ID_TYPE` on the columns `USER_ID` and `TYPE` to allow a faster search in the admin UI for events of a specific user and event type.
If the table contain more than 300000 entries, {project_name} will skip the index creation by default during the automatic schema migration and instead log the SQL statement on the console during migration to be applied manually after {project_name}'s startup.
See the link:{upgradingguide_link}[{upgradingguide_name}] for details on how to configure a different limit.
=== Encryption algorithms for SAML updated
When a SAML client was enabled to *Encrypt Assertions*, the assertion included in the SAML response was encrypted following the link:https://www.w3.org/TR/xmlenc-core1/[XML Encryption Syntax and Processing] specification. The algorithms used for encryption were fixed and outdated. Since this release, default encryption options are up to date and better suited in terms of security. Besides, the encryption details are also configurable, just in case a specific client needs a different set of algorithms to work properly. New attributes can be defined in the client to specify the exact algorithms used for encryption. The Admin console displays them in the client tab *Settings*, section *Signature and Encryption*, when the *Encrypt Assertions* option is enabled in the *Keys* tab.

7
model/jpa/src/main/resources/META-INF/jpa-changelog-26.4.0.xml
View File

@ -21,4 +21,11 @@
<customChange class="org.keycloak.connections.jpa.updater.liquibase.custom.JpaUpdate26_4_0_SamlEncryptionAttributes"/>
</changeSet>
<changeSet author="keycloak" id="26.4.0-51321">
<createIndex tableName="EVENT_ENTITY" indexName="IDX_EVENT_ENTITY_USER_ID_TYPE">
<column name="USER_ID" type="VARCHAR(255)" />
<column name="TYPE" type="VARCHAR(255)" />
</createIndex>
</changeSet>
</databaseChangeLog>