PingOne for Enterprise is an identity-as-a-service (IDaaS) and single sign-on (SSO) platform. It allows enterprises to give their users federated access to applications. In this guide, we integrate the PingOne IdP to authenticate users into the Wazuh platform.

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

  1. PingOne Configuration

  2. Wazuh indexer configuration

  3. Wazuh dashboard configuration

PingOne Configuration

  1. Create an account in Ping Identity. Request a free trial if you don't have a paid license.

  2. Go to PingOne and sign in with your Ping Identity account.

  3. Create an application in Connections.

    1. Navigate to Connections > Applications > Add Application and give it a name. In our case, the name is wazuh-sso.

    2. Proceed to the Choose Application Type section, and select SAML Application > Configure.

    3. Select Manually Enter on the Provide App Metadata section and add the following configuration, replacing <WAZUH_DASHBOARD_URL> with the corresponding value:

      • ACS URLs: https://<WAZUH_DASHBOARD_URL>/_opendistro/_security/saml/acs

      • Entity ID: wazuh-saml

    4. On the Configuration tab, click on the edit icon and add the following information:


      • SLO BINDING: HTTP Redirect

      • ASSERTION VALIDITY DURATION: 3600 (for one hour token validity)

      • VERIFICATION CERTIFICATE (OPTIONAL): Load a PUBLIC CERTIFICATE that corresponds to the PRIVATE KEY that is going to be used on the sp.signature_private_key_filepath of the config.yml configuration file on the Wazuh indexer instance. This is necessary as all the logout requests must be signed.

    5. Click on the Attribute Mappings tab, select the edit icon, click on Add and insert the following configuration:

      Roles = Group Names

      The Roles attribute will be used later as the sp.entity_id in the Wazuh indexer configuration file.

    6. Click on the Required checkbox, and click on Save.

  4. Create a group and assign users.

    1. Navigate to Identities > Groups, and click on the + sign. Select the name of the Group, in this case, wazuh-readonly.

    2. To assign users, open the created Group, go to the Users tab and select Add Individually. Add all the members that must log in to the Wazuh dashboard, and click on Save when done.

  5. Activate the application and note the necessary parameters.

    1. Navigate to Connections, select Applications, and enable the application.

    2. Take note of the following parameters from the configuration page of the application. This information will be used in the next step.

      • ISSUER ID: It'll be in the form

      • IDP METADATA URL: It’ll be in the form

      • exchange_key: If you open the IDP METADATA URL you'll find the X509 Certificate section, this will be used as the exchange_key.

Wazuh indexer configuration

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

  1. Place the private key file 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/securityconfig/PRIVATE_KEY
  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 the challenge flag to false.

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

            description: "Authenticate via HTTP Basic against internal users database"
            http_enabled: true
            transport_enabled: true
            order: 0
              type: "basic"
              challenge: false
              type: "intern"
            http_enabled: true
            transport_enabled: false
            order: 1
              type: saml
              challenge: true
                  metadata_url: IDP METADATA URL
                  entity_id: ISSUER ID
                  entity_id: wazuh-saml
                  signature_private_key_filepath: /etc/wazuh-indexer/opensearch-security/PRIVATE_KEY
                  forceAuthn: true
                kibana_url: https://<WAZUH_DASHBOARD_URL>
                roles_key: Roles
                exchange_key: 'MIIJ6DLSAAbAmAJHSgIWYia.........'
              type: noop

    Ensure to change the following parameters to their corresponding value:

    • idp.metadata_file

    • idp.entity_id

    • sp.entity_id

    • sp.signature_private_key_filepath

    • 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/ -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 -nhnv

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

    The command output must be similar to the following:

    Security Admin v7
    Will connect to ... 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

Wazuh 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 Wazuh 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 name of the group you created in PingOne 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.

      - default:
          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 Wazuh dashboard. To map the backend role to Wazuh, follow these steps:

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

      Wazuh 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 name you gave to your group in PingOne configuration, in our case, this is wazuh-readonly.

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

  3. Edit the Wazuh 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 Wazuh dashboard service.

    # systemctl restart wazuh-dashboard
  5. Test the configuration. Go to your Wazuh dashboard URL and log in with your Ping One account.