It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.

The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Secure your 5.x and 6.x clusters with LDAP or Active Directory Sign Outgoing SAML Message »
Elastic Docs ›Elastic Cloud Enterprise Reference [2.2] ›Administering deployments ›Secure your clusters

Secure your clusters with SAML

edit

Secure your clusters with SAML

edit

These steps show how you can secure your Elasticsearch clusters and Kibana instances in a deployment by using a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication.

The SAML credentials are valid against the deployment, not the ECE platform. You can try out our beta release of role-based access control for the platform.

Before you begin

edit

Elastic Cloud Enterprise supports SAML with Elastic Stack version 6.4 and later.

The steps in this section require an understanding of SAML, specifically the SAML 2.0 Web Browser SSO Profile. To learn more about SAML, see:

Configure your 7.x cluster to use SAML

edit

You must edit your cluster configuration, sometimes also referred to as the deployment plan, to point to the SAML IdP before you can complete the configuration in Kibana.

  1. Create or use an existing deployment that includes a Kibana instance version 6.4 or later.
  2. Copy the Kibana endpoint URL.

  3. Update your Elasticsearch user settings for the saml realm and specify your IdP provider configuration:

xpack:
  security:
    authc:
      realms:
        saml: <1>
          saml1: <2>
            order: 2
            attributes.principal: "nameid:persistent" <3>
            attributes.groups: "groups" <4>
            idp.metadata.path: "<check with your idp provider>" <5>
            idp.entity_id: "<check with your idp provider>" <6>
            sp.entity_id: "KIBANA_ENDPOINT_URL/" <7>
            sp.acs: "KIBANA_ENDPOINT_URL/api/security/v1/saml"
            sp.logout: "KIBANA_ENDPOINT_URL/logout"

+ <1> Specifies the authentication realm service. <2> The SAML realm name. Note that cloud-saml is reserved for internal use only and you cannot use it. Choose a different name, such as the one shown in the example. <3> Defines the SAML attribute that is going to be mapped to the principal (username) of the authenticated user in Kibana. In this example, nameid:persistent maps the NameID with the urn:oasis:names:tc:SAML:2.0:nameid-format:persistent format from the Subject of the SAML Assertion. See the attribute mapping documentation for details and available options. <4> Defines the SAML attribute used for role mapping when configured in Kibana. Common choices are groups or roles. The values for both attributes.principal and attributes.groups depend on the IdP provider, so be sure to review their documentation. See the attribute mapping documentation for details and available options. <5> The file path or the HTTPS URL where your IdP metadata is available, such as https://idpurl.com/sso/saml/metadata. If you configure a URL you need to make ensure that your Elasticsearch cluster can access it. <6> The SAML EntityID of your IdP. This can be read from the configuration page of the IdP, or its SAML metadata, such as https://idpurl.com/entity_id. <7> Replace KIBANA_ENDPOINT_URL with the one noted in the previous step, such as sp.entity_id: https://d1a45bf330b74c248d7cc2e0ead8e359.192.168.44.10.ip.es.io:9243/, including the slash at the end.

  1. By default, users authenticating via SAML have no roles assigned to them. For example, if you want all your users authenticating with SAML to get access to Kibana, issue the following request to Elasticsearch:

POST /_xpack/security/role_mapping/SAML1_TO_KIBANAUSER <1> { "enabled": true, "roles": [ "kibana_user" ], <2> "rules": { <3> "field": { "realm.name": "saml1" } }, "metadata": { "version": 1 } }

+ <1> The mapping name <2> The Elastic Stack role to map to <3> A rule specifying the SAML role to map from

  1. Alternatively, if you want the users that belong to the group elasticadmins in your identity provider to be assigned the superuser role in your Elasticsearch cluster, issue the following request to Elasticsearch:

POST /_xpack/security/role_mapping/SAML1_ELASTICADMIN_TO_SUPERUSER <1> { "enabled": true, "roles": [ "superuser" ], <2> "rules": { "all" : [ <3> { "field": { "realm.name": "saml1" } }, { "field": { "groups": "elasticadmins" } } ]}, "metadata": { "version": 1 } }

+ <1> The mapping name <2> The Elastic Stack role to map to <3> A rule specifying the SAML role to map from

+ NOTE: In order to use the field groups in the mapping rule, you need to have mapped the SAML Attribute that conveys the group membership to attributes.groups in the previous step.

  1. Update Kibana in the user settings configuration to use SAML as the authentication provider:

xpack.security.authProviders: [saml] server.xsrf.whitelist: [/api/security/v1/saml] xpack.security.public: protocol: https hostname: d1a45bf330b74c248d7cc2e0ead8e159.192.168.44.10.ip.es.io <1> port: 9243

+ <1> The hostname from your Kibana endpoint URL

+ TIP: This configuration disables all other realms and only allows users to authenticate with SAML. If you wish to allow your native realm users to authenticate, you need to also enable the basic authProvider by setting xpack.security.authProviders: [saml, basic] in the configuration of Kibana. You can then access the Kibana login screen at https://d1a45bf330b74c248d7cc2e0ead8e159.192.168.44.10.ip.es.io:9243/login

  1. Optional: If your Identity Provider doesn’t publish its SAML metadata at an http URL, or if your Elasticsearch cluster cannot reach that URL, you can upload the SAML metadata as a file.

    1. Prepare a ZIP file with a custom bundle that contains your Identity Provider’s metadata (metadata.xml) inside of a saml folder.

      This bundle allows all Elasticsearch containers to access the metadata file.

    2. Update your Elasticsearch cluster configuration using the advanced configuration editor to use the bundle you prepared in the previous step. You need to modify the user_bundles JSON attribute similar to the following example snippet:

      {
  "cluster_name": "REPLACE_WITH_YOUR_CLUSTER_NAME",
  "plan": {

    ...

    "elasticsearch": {
      "version": "6.4.1",
      "user_bundles": [
        {
          "name": "saml-metadata",
          "url": "https://www.MYURL.com/saml-metadata.zip",
          "elasticsearch_version": "6.4.1"
        }
      ]
    }
  }

      The URLs that point to the ZIP file containing the bundle must be accessible to the deployment. Custom bundles are unzipped under the path /app/config/BUNDLE_DIRECTORY_STRUCTURE, where BUNDLE_DIRECTORY_STRUCTURE is the directory structure in the ZIP file. Make sure to save the file location where custom bundles get unzipped, as you will need it in the next step.

      In our example, the SAML metadata file will be located in the path /app/config/saml/metadata.xml:

      $ tree .
.
└── saml
      └── metadata.xml

    3. Adjust your saml realm configuration accordingly:

          idp.metadata.path: /app/config/saml/metadata.xml

      The path to the SAML metadata file that was uploaded

Configure your 6.x cluster to use SAML

edit

For 6.x deployments the configuration is slightly different. For step 3, you must specify the realm name, then define the realm type using the following example:

xpack:
  security:
    authc:
      realms:
        cloud-saml:
          type: saml
            order: 2

All of the other steps are the same.

« Secure your 5.x and 6.x clusters with LDAP or Active Directory Sign Outgoing SAML Message »