Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Moving section to the correct place #43105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ahus1 merged 1 commit into from
Oct 1, 2025
Merged

Moving section to the correct place #43105

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/documentation/release_notes/topics/26_4_0.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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.
Expand Down
Loading