Keycloak

Keycloak is an open source identity and access management tool. It provides user federation, strong authentication, user management, and fine-grained authorization for modern applications and services. In this guide, we integrate the KeyCloak IdP to authenticate users into the ThreatLockDown platform.

There are three stages in the single sign-on integration:

  1. KeyCloak configuration

  2. ThreatLockDown indexer configuration

  3. ThreatLockDown dashboard configuration

KeyCloak configuration

  1. Create a new realm. Log in to the Keycloak admin console, expand the master drop-down menu and click Add Realm. Input a name in the Realm name field; in our case, this is named Wazuh. Click on Create to apply this configuration.

  2. Create a new client. In the newly created realm, navigate to Clients > Create Client and modify the following parameters:

    • Client type: select SAML from the drop-down menu.

    • Client ID: input wazuh-saml. This is the SP Entity ID value which will be used later in the config.yml on the ThreatLockDown indexer instance.

    You can leave the rest of the values as default. Click Save to apply the configuration.

  3. Configure client settings.

    1. Navigate to Clients > Settings and ensure the Enabled button is turned on. Complete the section with these parameters:

      • Client ID: wazuh-saml

      • Name: Wazuh SSO

      • Valid redirect URIs: https://<WAZUH_DASHBOARD_URL>/*

      • IDP-Initiated SSO URL name: wazuh-dashboard

      • Name ID format: username

      • Force POST binding: ON

      • Include AuthnStatement: ON

      • Sign documents: ON

      • Sign assertions: ON

      • Signature algorithm: RSA_SHA256

      • SAML signature key name: KEY_ID

      • Canonicalization method: EXCLUSIVE

      • Front channel logout: ON

      Replace the WAZUH_DASHBOARD_URL field with the corresponding URL of your ThreatLockDown dashboard instance.

      The configuration must be similar to the highlighted blue rectangles:

      You can leave the rest of the values as default. Click Save to apply the configuration.

    2. Navigate to Clients > Keys and complete the section with these parameters:

      • Client signature required: Off

    3. Navigate to Clients > Advanced > Fine Grain SAML Endpoint Configuration and complete the section with these parameters:

      • Assertion Consumer Service POST Binding URL: https://<WAZUH_DASHBOARD_URL>/_opendistro/_security/saml/acs/idpinitiated

      • Logout Service Redirect Binding URL: https://<WAZUH_DASHBOARD_URL>

      You can leave the rest of the values as default. Click Save to apply the configuration.

  4. Create a new role. Navigate to Realm roles > Create role and complete the section with these parameters:

    • Role name: Input wazuh-readonly. This will be our backend role in the ThreatLockDown Indexer configuration.

    Click on Save to apply the configuration.

  5. Create a new user.

    1. Navigate to Users > Add user and fill in the required information.

      Click on Create to apply the configuration.

    2. Navigate to Users > Credentials > Set password and input a password for the newly created user. You will use these credentials to log in to the ThreatLockDown dashboard.

      Click on Save to apply the configuration.

  6. Create a new group and assign the user.

    1. Go to Groups > Create group and assign a name to the group. In our case, this is ThreatLockDown read only.

    2. Click on the newly created group, navigate to Members > Add member and select the user created in the previous step. Click on Add to add it to the group.

    3. In the newly created group details, go to Role Mapping > Assign role and select the wazuh-readonly role created in step 3. Click on Assign to apply the configuration.

  7. Configure protocol mapper.

    1. Navigate to Client scopes > role_list > Mappers > Configure a new mapper.

    2. Select Role list from the list as seen below:

    3. Complete the Add mapper section with these parameters:

      • Mapper type: Role list

      • Name: wazuhRoleKey. You can use any name here.

      • Role attribute name: Roles. This will be the roles_key on the ThreatLockDown Indexer configuration.

      • SAML Attribute NameFormat: Basic

      • Single Role Attribute: On

    Click on Save to apply the configuration.

  8. Note the necessary parameters from the SAML settings of Keycloak.

    1. The parameters already obtained during the integration are:

      • sp.entity_id: wazuh-saml

      • roles_key: Roles

      • kibana_url: https://<WAZUH_DASHBOARD_URL>

    2. To obtain the remaining parameters.

      1. Navigate to Clients and select the name of your client. In our case, this is wazuh-saml.

      2. Navigate to Action > Download adapter config, and ensure the Format option is Mod Auth Mellon files.

      3. Click on Download to download the remaining files.

    3. The downloaded files contain the idp.metadata.xml file and the sp.metadata.xml file.

      • The idp.entityID parameter is in the idp.metadata.xml file.

      • The exchange_key parameter is found in the ds:X509Certificate field in the idp.metadata.xml file.

ThreatLockDown indexer configuration

Edit the ThreatLockDown indexer security configuration files. We recommend that you back up these files before you carry out the configuration.

  1. Place the idp.metadata.xml and sp.metadata.xml files within the /etc/wazuh-indexer/opensearch-security/ directory. Set the file ownership to wazuh-indexer using the following command:

    chown wazuh-indexer:wazuh-indexer /etc/wazuh-indexer/opensearch-security/idp.metadata.xml
chown wazuh-indexer:wazuh-indexer /etc/wazuh-indexer/opensearch-security/sp.metadata.xml

  2. Edit the /etc/wazuh-indexer/opensearch-security/config.yml file and change the following values:

    • Set the order in basic_internal_auth_domain to 0, and set the challenge flag to false.

    • Include a saml_auth_domain configuration under the authc section similar to the following:

        authc:
...
      basic_internal_auth_domain:
        description: "Authenticate via HTTP Basic against internal users database"
        http_enabled: true
        transport_enabled: true
        order: 0
        http_authenticator:
          type: "basic"
          challenge: false
        authentication_backend:
          type: "intern"
      saml_auth_domain:
        http_enabled: true
        transport_enabled: false
        order: 1
        http_authenticator:
          type: saml
          challenge: true
          config:
            idp:
              metadata_file: '/etc/wazuh-indexer/opensearch-security/idp.metadata.xml'
              entity_id: 'http://192.168.XX.XX:8080/realms/Wazuh'
            sp:
              entity_id: wazuh-saml
              metadata_file: '/etc/wazuh-indexer/opensearch-security/sp.metadata.xml'
            kibana_url: https://<WAZUH_DASHBOARD_ADDRESS>
            roles_key: Roles
            exchange_key: 'MIICajCCAdOgAwIBAgIBAD.........'
        authentication_backend:
          type: noop

    Ensure to change the following parameters to their corresponding value:

    • idp.metadata_file

    • idp.entity_id

    • sp.entity_id

    • sp.metadata_file

    • kibana_url

    • roles_key

    • exchange_key

  3. Run the securityadmin script to load the configuration changes made in the config.yml file.

    # export JAVA_HOME=/usr/share/wazuh-indexer/jdk/ && bash /usr/share/wazuh-indexer/plugins/opensearch-security/tools/securityadmin.sh -f /etc/wazuh-indexer/opensearch-security/config.yml -icl -key /etc/wazuh-indexer/certs/admin-key.pem -cert /etc/wazuh-indexer/certs/admin.pem -cacert /etc/wazuh-indexer/certs/root-ca.pem -h localhost -nhnv

    The -h flag specifies the hostname or the IP address of the ThreatLockDown indexer node. Note that this command uses localhost, set your ThreatLockDown indexer address if necessary.

    The command output must be similar to the following:

    Security Admin v7
Will connect to localhost:9200 ... done
Connected as "CN=admin,OU=Wazuh,O=Wazuh,L=California,C=US"
OpenSearch Version: 2.10.0
Contacting opensearch cluster 'opensearch' and wait for YELLOW clusterstate ...
Clustername: wazuh-cluster
Clusterstate: GREEN
Number of nodes: 1
Number of data nodes: 1
.opendistro_security index already exists, so we do not need to create one.
Populate config from /etc/wazuh-indexer/opensearch-security
Will update '/config' with /etc/wazuh-indexer/opensearch-security/config.yml
   SUCC: Configuration for 'config' created or updated
SUCC: Expected 1 config types for node {"updated_config_types":["config"],"updated_config_size":1,"message":null} is 1 (["config"]) due to: null
Done with success

ThreatLockDown dashboard configuration

  1. Create a new role mapping for the backend role. Follow these steps to create a new role mapping, and grant read-only permissions to the backend role.

    1. Log into the ThreatLockDown dashboard as administrator.

    2. Click the upper-left menu icon ☰ to open the options, go to Indexer/dashboard management > Security, and then Roles to open the roles page.

    3. Click Create role, complete the empty fields with the following parameters, and then click Create to complete the task.

      • Name: Assign a name to the role.

      • Cluster permissions: cluster_composite_ops_ro

      • Index: *

      • Index permissions: read

      • Tenant permissions: Select global_tenant and the Read only option.

    4. Select the newly created role.

    5. Select the Mapped users tab and click Manage mapping.

    6. Under Backend roles, add the value of the Role name attribute in Keycloak configuration and click Map to confirm the action. In our case, the backend role is wazuh-readonly.

  2. Check the value of run_as in the /usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml configuration file. If run_as is set to false, proceed to the next step.

    hosts:
  - default:
      url: https://localhost
      port: 55000
      username: wazuh-wui
      password: "<wazuh-wui-password>"
      run_as: false

    If run_as is set to true, you need to add a role mapping on the ThreatLockDown dashboard. To map the backend role to Wazuh, follow these steps:

    1. Click ☰ to open the menu on the ThreatLockDown dashboard, go to Server management > Security, and then Roles mapping to open the page.

      ThreatLockDown role mapping

    2. Click Create Role mapping and complete the empty fields with the following parameters:

      • Role mapping name: Assign a name to the role mapping.

      • Roles: Select readonly.

      • Custom rules: Click Add new rule to expand this field.

      • User field: backend_roles

      • Search operation: FIND

      • Value: Assign the value of the realm role in Keycloak configuration. In our case, this is wazuh-readonly.

      Create ThreatLockDown role mapping

    3. Click Save role mapping to save and map the backend role with ThreatLockDown as read-only.

  3. Edit the ThreatLockDown dashboard configuration file. Add these configurations to /etc/wazuh-dashboard/opensearch_dashboards.yml. We recommend that you back up these files before you carry out the configuration.

    opensearch_security.auth.type: "saml"
server.xsrf.allowlist: ["/_opendistro/_security/saml/acs", "/_opendistro/_security/saml/logout", "/_opendistro/_security/saml/acs/idpinitiated"]
opensearch_security.session.keepalive: false

  4. Restart the ThreatLockDown dashboard service using this command:

    # systemctl restart wazuh-dashboard

  5. Test the configuration. Go to your ThreatLockDown dashboard URL and log in with your Keycloak account.