If configured, Elastic Stack will sign outgoing SAML messages.
As a prerequisite, you need to generate a signing key and a self-signed
certificate. You need to share this certificate with your SAML Identity Provider
so that it can verify the received messages. The key needs to be unencrypted.
The exact procedure is system dependent, you can use for example
openssl req -new -x509 -days 3650 -nodes -sha256 -out saml-sign.crt -keyout saml-sign.key
Place the files under
saml folder and add them to the existing SAML bundle, or
create a new one as described above.
In our example, the certificate and the key will be located in the path
$ tree . . └── saml ├── saml-sign.crt └── saml-sign.key
Make sure the bundle is included with your deployment (see above).
Adjust your realm configuration accordingly:
+ <1> The path to the SAML signing certificate that was uploaded.
+ <2> The path to the SAML signing key that was uploaded.
When configured with a signing key and certificate, Elastic Stack will sign all outgoing messages (SAML Authentication Requests, SAML Logout Requests, SAML Logout Responses) by default. This behavior can be altered by configuring `signing.saml_messages` appropriately with the comma separated list of messages to sign. Supported values are `AuthnRequest`, `LogoutRequest` and `LogoutResponse` and the default value is `*`.
+ <1> This configuration will ensure that only SAML Authentication Requests will be sent signed to the Identity Provider
Following optional realm settings are supported:
force_authnSpecifies whether to set the
ForceAuthnattribute when requesting that the IdP authenticate the current user. If set to
true, the IdP is required to verify the user’s identity, irrespective of any existing sessions they might have. Defaults to
idp.use_single_logoutIndicates whether to utilise the Identity Provider’s
<SingleLogoutService>(if one exists in the IdP metadata file). Defaults to
After completing these steps, you can log into Kibana by authenticating against your SAML IdP. If you encounter any issues with the configuration, please take a look at our SAML troubleshooting page which contains information about common issues and suggestions for their resolution.