Skip to main content

&frankly SAML integration

Multi-Factor Authentication (MFA) is an extra layer of security used when logging into websites or apps. Individuals are authenticated through more than one required security and validation procedure that only they 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, offers a simple method for adding MFA to &frankly via its SAML solution.


  • 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 privileges for &frankly.

&frankly configuration

In this section, you'll configure &frankly 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 &frankly with an administrative account.

  3. From the left navigation, select Account > User management.

  4. Scroll down to the Authentication section and make a note of your company ID (Company Identifier) value for the Arculix configuration.

  5. Click Configure single-sign on and change it to Enterprise Sign-on (SAML).

  6. Click Choose File and upload the Arculix metadata that was downloaded earlier.

  7. Click Save.

Arculix SAML configuration as an Identity Provider (IdP)

In this section, you'll add an application for &frankly 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, &frankly.


    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 URL in the following format:<company id>

    Use the company ID you copied in Step 4 of the @frankly configuration.

    Log in URL 

    Enter the login URL in the following format:<company id>

    Use the company ID you copied in Step 4 of the @frankly configuration.

    NameID Format 

    Set to Email Address.

    Name Identifier 

    Set to Email.

    ACS URL 

    Enter the ACS URL in the following format:<tenant id>

    Use the company ID you copied in Step 4 of the @frankly configuration.


    Set to RSA-SHA256.

  5. At the bottom of the page, click Add New Attribute Assertion and populate the fields like the table below:

    Friendly Name



    Name Format













  6. Save your changes.

Test your application integration

  1. Go to the &frankly login URL, enter your email, and click Next.

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

    Application login page with QR code
  3. After successful authentication, select your preferred MFA method to approve access to the &frankly application.

    Select MFA method
  4. Finally, you will be redirected and logged in to &frankly.


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.