Skip to main content

Atlassian Cloud 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.

Acceptto™, as a SAML provider, improves the user login experience for Atlassian users with convenient MFA, and offers a simple SAML solution for adding MFA and single sign-on (SSO) on the Atlassian portal.


  • Acceptto account with a configured Identity Provider and LDAP Agent.

    For more information, see the LDAP Agent deployment guide.

  • An Atlassian Cloud user account with administrative access.

  • User account with administrative privileges for the Acceptto eGuardian dashboard.

Atlassian Cloud configuration

In this section, you'll configure Atlassian Cloud as a service provider (SP).

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

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

    View metadata:<myorganization>/saml/metadata

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

  2. Log in to your Atlassian Admin portal as an administrator.

  3. Select the Security tab and click SAML single sign-on.

    SAML configuration page
  4. Click Add SAML configuration and configure the following:

    Identity provider Entity ID

    Enter the entityID found in the Acceptto metadata.

    For example,<myorganization>/saml.

    Identity provider SSO URL

    Enter the SingleSignOnService found in the Acceptto metadata.

    For example,<myorganization>/saml/auth.

    Public x509 certificate

    Copy the certificate downloaded from Acceptto in Step 1.

  5. Click Save.

Acceptto SAML configuration as an Identity Provider (IdP)

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

  1. Log in to the Acceptto Dashboard 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, Atlassian Cloud.


    Set to SAML Service Provider.

    Out of Band Methods

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

    For example, It'sMe 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/EntityID of your Atlassian Cloud provided in the Atlassian SAML configuration section.

    Sign in URL

    Enter the link used by your users to access Atlassian Cloud.

    NameID Format

    Set to Email Address.

    Name Identifier

    Set to Email.


    Enter the Assertion Consumer Service URL provided in the Atlassian SAML configuration section.

  5. Click Save.

Test your application integration

  1. Go to your Atlassian login portal.

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

    SSO login
  3. After successful authentication, select your preferred MFA method to approve access to the Atlassian Cloud application.

    Select MFA method
  4. Finally, you will be redirected to the Atlassian cloud portal page via an easy and passwordless authentication 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.