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.
Create an account in Ping Identity. Request a free trial if you don't have a paid license.
Go to PingOne and sign in with your Ping Identity account.
Create an application in Connections.
Navigate to Connections > Applications > Add Application and give it a name. In our case, the name is
Proceed to the Choose Application Type section, and select SAML Application > Configure.
Select Manually Enter on the Provide App Metadata page and add the following configuration, replacing
<WAZUH_DASHBOARD_URL>with the corresponding value:
On the Configuration tab, click on the edit icon and add the following information:
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
config.ymlconfiguration file on the Wazuh indexer instance. This is necessary as all the logout requests must be signed.
Click on the Attribute Mappings tab, select the edit icon, click on Add and insert the following configuration:
Rolesattribute will be used later as the
sp.entity_idin the Wazuh indexer configuration file.
Click on the Required checkbox, and click on Save.
Create a group and assign users.
Navigate to Identities > Groups, and click on the + sign. Select the name of the Group, in this case,
To assign users, open the created Group, go to the Users tab and select Add Users Individually. Add all the members that must log in to the Wazuh dashboard, and click on Save when done.
Activate the application and note the necessary parameters.
Navigate to Connections, select Applications, and enable the application.
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 https://auth.pingone.com/...
IDP METADATA URL: It’ll be in the form https://auth.pingone.com/...
exchange_key: If you open IDP IDP METADATA URL you'll find the X509 Certificate section, this will be used as the
Edit the Wazuh indexer security configuration files. We recommend that you back up these files before you carry out the configuration.
Place the private key file within the
/etc/wazuh-indexer/opensearch-security/directory. Set the file ownership to
wazuh-indexerusing the following command:
# chown wazuh-indexer:wazuh-indexer /etc/wazuh-indexer/opensearch-security/securityconfig/PRIVATE_KEY
/etc/wazuh-indexer/opensearch-security/config.ymlfile and change the following values:
saml_auth_domainconfiguration under the
authcsection 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_url: IDP METADATA URL entity_id: ISSUER ID sp: 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.........' authentication_backend: type: noop
Ensure to change the following parameters to their corresponding value:
securityadminscript to load the configuration changes made in the
# 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
-hflag specifies the hostname or the IP address of the Wazuh indexer node. Note that this command uses localhost, set your Wazuh 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.6.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 Done with success
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.
Log into the Wazuh dashboard as administrator.
Click the upper-left menu icon ☰ to open the options, select Security, and then Roles to open the roles page.
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.
Tenant permissions: Select
Select the newly created role.
Select the Mapped users tab and click Manage mapping.
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
Check the value of
/usr/share/wazuh-dashboard/data/wazuh/config/wazuh.ymlconfiguration file. If
run_asis 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
run_asis set to
true, you need to add a role mapping on the Wazuh dashboard. To map the backend role to Wazuh, follow these steps:
Click the upper-left menu icon ☰ to open the available options.
Click Wazuh to open the Wazuh dashboard menu, select Security, and then Roles mapping to open the page.
Click Create Role mapping and complete the empty fields with the following parameters:
Role mapping name: Assign a name to the role mapping.
Custom rules: Click Add new rule to expand this field.
Value: Assign the name you gave to your group in PingOne configuration, in our case, this is
Click Save role mapping to save and map the backend role with Wazuh as read-only.
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"]
Restart the Wazuh dashboard service.
# systemctl restart wazuh-dashboard
# service wazuh-dashboard restart
Test the configuration. Go to your Wazuh dashboard URL and log in with your Ping One account.