Skip to main content

Breezy HR 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 single sign-on (SSO) MFA to Breezy HR through 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 Breezy HR.

Breezy HR configuration

In this section, you'll configure Breezy HR 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 Breezy HR instance and in the top left, click the gear icon.

  3. Select Recruiting Preferences > Integrations.

  4. On the Integrations page, select the Single Sign-On check box and click Apply Filter.

  5. Click the Settings button in the SAML category.

  6. The SAML SSO Settings page appears. Do the following:

    Single Sign-On URL

    Copy this URL for Arculix configuration.

    SAML Metadata File

    Click Upload Metadata File and upload the metadata file downloaded from Arculix.

  7. Click Save Changes.

Arculix SAML configuration as an Identity Provider (IdP)

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


    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 Entity ID URL provided by Breezy HR.

    For example,<yourorganization>/metadata.xml

    Log in URL 

    Enter the Log in URL provided by Breezy HR.

    For example,<yourorganization>

    NameID Format 

    Set to Email Address.

    Name Identifier 

    Set to Email.

    ACS URL 

    Enter the ACS URL provided by Breezy HR.

    For example,<yourorganization>

    Single Logout URL

    Enter the SLO URL provided by Breezy HR.

    For example,<yourorganization>


    Set to RSA-SHA256.

  5. Save your changes.

Test your application integration

  1. Go to your Breezy HR SAML URL.

    For example,<yourorganization>.

  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 Breezy HR application.

    Select MFA method


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.