Skip to main content

PingOne SAML integration

Multi-factor authentication (MFA) is an extra layer of security used when logging into websites or apps to authenticate users through more than one required security and validation procedure that only you know or have access to.

Security Assertion Markup Language (SAML) is a protocol for authenticating to web applications. SAML allows federated apps and organizations to communicate and trust one another’s users.

Arculix by SecureAuth, as a SAML provider, improves the user login experience for PingOne users through its SSO-MFA solution.

Watch a video about this integration with Arculix in under 5 minutes.


  • Configured Arculix instance and user account with administrative privileges for Arculix.

  • Configured Arculix LDAP Agent.

    For more information, see the Arculix LDAP Agent deployment guide.

  • User account with administrative access for PingOne.

PingOne configuration

In this section, you will configure PingOne as a service provider (SP).

  1. Download the SAML metadata and certificate for your organization from Arculix.

    Metadata download:<myorganization>/saml/download/metadata

    View metadata:<myorganization>/saml/metadata

    Certificate download:<myorganization>/saml/download/cert

  2. Log in to your PingOne Admin console as an administrator.

  3. In the left panel, select Connections > External IDPs, and click Add Provider.

    Add provider
  4. On the Add a Social or Custom Identity Provider page, click SAML.

    Select SAML
  5. In the Create Profile section, enter a unique Name and Description, and click Continue.

  6. In the Configure PingOne Connection section, copy the PingOne (SP) ENTITY ID URL for the Arculix configuration, and click Continue.

    Copy EntityID
  7. In the Configure IDP Connection section, set the following configurations:

    Provide IdP Metadata

    Choose the Import Metadata option and upload the Arculix metadata file you downloaded in Step 1

    ACS Endpoint

    Copy the ACS Endpoint URL for the Arculix configuration.

    Configure IDP connection
  8. Click Save and Continue.

  9. In the Map Attributes section, click Add Attribute and set the following:

    PingOne User Profile Attribute

    Set to Email Address.

    SAML Attribute

    Set to

    Map attributes
  10. Click Save & Finish.

    Next, continue with the PingOne configuration to add Arculix to an authentication policy.

Enable Arculix and add an authentication policy in PingOne

In this section, enable Arculix as an external identity provider and add an authentication policy to use Arculix.

  1. In the left panel, select Connections > External IDPs.

  2. Move the slider ON to enable Arculix as a newly added identity provider and click the pencil icon to make edits.

  3. Select the Registration tab.

  4. In the Registration Details > Population section, select the population, and click Save.

  5. In the left panel, select Experiences > Authentication.

  6. On the Authentication Policies page, click Add Policy.

  7. Set the following configurations for Arculix as an external identity provider:

    Policy Name

    Enter name of policy.

    External Identity Provider

    Select Arculix from the list and again in the next sub list.

    Enable Registration

    Select this check box.


    Select the population group.

  8. Save your changes.

  9. In the left panel, select Connections > Applications.

  10. Select PingOne Application Portal and copy the Home Page URL for the Arculix configuration.

    Repeat this step as needed for any another application.

    Applications page
  11. On the PingOne Application Portal page, select the Policies tab, and click Add Polices.

    Add Policies
  12. Select Arculix and click Add.

  13. Save your changes.

Arculix SAML configuration as an Identity Provider (IdP)

In this section, you'll add an application for PingOne and set the SAML configuration settings. This will be the Identity Provider (IdP) side of the configuration.

  1. Log in to Arculix with an administrative account and go to Applications.

  2. Click Create New Application.

    Create new application
  3. In the New Application form, on the General tab, set the following configurations:


    Set the name of the application. This is the name to display for push notifications, in the Admin panel, Application portal, and audit logs.

    For example, PingOne.


    Set to SAML Service Provider.

    Out of Band Methods 

    Select the allowed methods end users can choose to approve MFA requests.

    For example, Arculix Mobile app (push notifications), SMS, or Security Key.

    Message for MFA Requests 

    Optional. Type a message displayed to end users when sending an MFA request via push notification, SMS, or email.

  4. Select the SAML Service Provider Configuration tab, and set the following configurations:

    Issuer or Entity ID 

    Enter the Issuer or Entity ID of your PingOne instance.

    For example,<identifier>

    Log in URL 

    Enter the home page URL for your PingOne instance.

    For example,<identifier>/myapps/

    NameID Format 

    Set to Email Address.

    Name Identifier 

    Set to Email.

    ACS URL 

    Enter the Assertion Consumer Service of your PingOne instance.

    For example,<identifier>/saml20/sp/acs

  5. Save your changes.

Test your application integration

  1. Go to your PingOne Application Portal page and log in.

  2. You will be redirected to the Arculix SSO page.

    Application login page with email
  3. After successful authentication, select your preferred MFA method to approve access to the PingOne application.

    Select MFA method
  4. Finally, you are redirected to your PingOne Application Portal landing page.

    PingOne portal page


If you have questions or need assistance, contact SecureAuth Support.


Want to learn more about our MFA solutions? Contact our Professional Services for a demo today.


All product names, trademarks, and registered trademarks are the property of their respective owners.

All company, product, and service names used in this document are for identification purposes only. The use of these names, trademarks, and brands do not constitute an endorsement by the SecureAuth Corporation.