The following table details the required and optional attributes to be configured in the assertion attribute contract.

Attribute Name Description Required / Optional

SAML_SUBJECT

Email Address

Required

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname

First Name

Required

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname

Surname

Required

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

ID (not email)

Required

The following table details the references that are used within this guide that are environment specific. Replace these with the suitable value for your environment.

Reference Description

<TenantSSOID>

Tenant single sign-on (SSO) ID, retrieved from Atlassian Cloud SAML Single Sign-on configuration as part of EntityID and Assertion Consumer Service (ACS) URL.
  1. Create a PingOne Application for Atlassian Cloud.
    Note:

    The following configuration is untested, and is provided as an example. Additional steps might be required.

    1. In Atlassian Cloud, go to Security > SAML Single Sign-on and sign on to Atlassian Cloud as an administrator.
    2. Make a note of the Entity ID and ACS URL values.
    3. Sign on to PingOne for Enterprise and go to Applications > Application Catalog.
    4. On the SAML tab, in the Add Application list, select Search Application Catalog.

      Screen capture of the PingOne admin page My Applications page open to the SAML tab showing the Add Applications list.
    5. Search for Atlassian and then click the Atlassian Cloud row.

      Screen capture of the PingOne admin page Application Catalog tab.
    6. Click Setup.
    7. In the Signing Certificate list, select the appropriate signing certificate.
    8. Review the steps, and make a note of the PingOne SaaS ID, IdP ID, Single Sign-On URL, and Issuer values shown.

      Screen capture of the PingOne admin page showing the SSO Instructions fields for the Application Catalog.
    9. Click Continue to Next Step.
    10. Enter the following.
      Attribute Directions URL

      ACS URL

      Enter the ACS URL from step 1b.

      https://auth.atlassian.com/login/callback?connection=saml-<tenantSSOID>

      Entity ID

      Enter the Entity ID from step 1b.

      https://auth.atlassian.com/saml/<tenantSSOID>

      Screen capture of the PingOne admin page showing the Connection Configuration steps for the Application Catalog. The ACS URL and Entity ID fields are highlighted in red.
    11. Click Continue to Next Step.
    12. Configure the Attribute Mapping section.
      Application Attribute Identity Bridge Attribute or Literal Value

      SAML_SUBJECT

      Select a suitable attribute containing the email address.

      givenname

      Select a suitable attribute containing the user’s first name.

      surname

      Select a suitable attribute containing the user’s last name.

      name

      Select a suitable attribute containing the user’s unique ID.

      Note:

      This should not be the email address.

      Screen capture of the PingOne admin page showing the Attribute Mapping fields on the Application Catalog. The Identity Bridge: Attribute or Literal Value column fields are highlighted in red.
    13. Click Continue to Next Step.
    14. Update the Name, Description, and Category fields as required.

      Screen capture of the PingOne admin page showing the PingOne App Customization - Atlassian Cloud fields.
    15. Click Continue to Next Step.
    16. Add the user groups for the application.

      Screen capture of the PingOne admin page showing the Group Access fields for the Application Catalog.
    17. Click Continue to Next Step.
    18. Review the settings.
    19. Copy the Single Sign-On (SSO) URL value to a temporary location.
      This is the IdP-initiated SSO URL that you can use for testing.
    20. Make a note of the PingOne Issuer and PingOne idpid values.
      You will use these in the Atlassian Cloud configuration.

      Screen capture of the PingOne admin page showing the Review Setup fields for the Application Catalog. The idpid and Issuer fields are highlighted in red.
    21. On the Signing Certificate line, click Download. Click Finish.

      Screen capture of the PingOne admin page showing the Review Setup fields for the Application Catalog. The Signing Certificate Download button and the Finish buttons are highlighted.

      You will use this in the Atlassian Cloud configuration.


      Screen capture of the PingOne admin page showing all of the available applications added to an account for My Applications.
  2. Configure the PingOne IdP connection for Atlassian Cloud.
    Note:

    The following configuration is untested and is provided as an example. Additional steps might be required.

    1. In Atlassian Cloud, go to Security > SAML Single Sign-on and sign on to Atlassian Cloud as an administrator.
    2. Click Add SAML Configuration.
    3. Enter the following:
      • In the Identity Provider Entity ID field, enter the Issuer value from the PingOne configuration.
      • In the Identity Provider SSO URL field, enter https://sso.connect.pingidentity.com/sso/idp/SSO.saml2?idpid=<idpid>, replacing <idpid> with the one from the PingOne configuration.
      • In a text editor, open the certificate you downloaded during the PingOne configuration, and paste the contents of the certificate into the Public x509 Certificate field.
    4. Click Save Configuration.