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

Moving section to the correct place

Browse Source 
Closes #43104

Signed-off-by: Alexander Schwartz <alexander.schwartz@ibm.com>
This commit is contained in:
Alexander Schwartz 2025-10-01 13:08:17 +02:00 committed by GitHub
parent e280d32ad9
commit 771ef3e840
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/documentation/release_notes/topics/26_4_0.adoc
View File

@ -68,6 +68,10 @@ endif::[]
Identity providers are now able to federate client authentication. This allows clients to authenticate with SPIFFE JWT SVIDs,
Kubernetes service account tokens, or tokens issued by an OpenID Connect identity provider.
ifeval::[{project_community}==true]
This feature is currently preview, and expected to become supported in 26.5.
endif::[]
== Automatic certificate management for SAML clients
The SAML clients can now be configured to automatically download the signing and encrypting certificates from the SP entity metadata descriptor endpoint. In order to use this new feature, in the client *Settings* tab, section *Signature and Encryption*, configure the *Metadata descriptor URL* option (the URL where the SP metadata information with the certificates is published) and activate *Use metadata descriptor URL*. The certificates will be automatically downloaded and cached in the `public-key-storage` SPI from that URL.
@ -91,10 +95,6 @@ Users can now update their email addresses in a more secure and consistent flow.
For more information, see link:{adminguide_link}#_update-email-workflow[Update Email Workflow].
ifeval::[{project_community}==true]
This feature is currently preview, and expected to become supported in 26.5.
endif::[]
== Optional email domain for organizations
In earlier versions, each organization required at least one email domain, which was a limitation for some scenarios.