Uploaded image for project: 'Identity'
  1. Identity
  2. ID-80

Support SAML integration with Cloud apps

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Cloud SAML single sign-on

      SAML single sign-on is available as part of Identity Manager. More information about Identity Manager.
       
      Read up on how to configure SAML single sign-on for our Cloud products.
       
      Thanks for all of your feedback and discussion on this ticket. We'll continue to monitor and respond to it, as well as take on board your requests for future enhancements.
       
      We receive a lot of requests for new features and improvements, so if you'd like to better understand how we make roadmap decisions, please read: https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy

        1. 02111600.JPG
          194 kB
          Markus Bühler
        2. 2016-12-06_09-33-39.jpg
          78 kB
          Markus Bühler
        3. Claims.PNG
          15 kB
          rmeyer651983655
        4. endpoint.PNG
          15 kB
          rmeyer651983655
        5. fields.PNG
          20 kB
          rmeyer651983655
        6. Identifiers.PNG
          15 kB
          rmeyer651983655
        7. image001.png
          11 kB
          André K.
        8. image003.png
          11 kB
          André K.
        9. image004.png
          14 kB
          André K.
        10. image005.png
          10 kB
          André K.
        11. image-2017-02-21-23-25-35-930.png
          51 kB
          HA
        12. SAC.PNG
          12 kB
          rmeyer651983655
        13. screenshot-1.png
          49 kB
          Erik Segerstolpe
        14. transform.PNG
          23 kB
          rmeyer651983655

            [ID-80] Support SAML integration with Cloud apps

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3258592 ] New: JAC Suggestion Workflow 3 [ 3643928 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]

            Gabriel Muller (Inactive) added a comment -

            Hi all,

            Atlassian added the documentation Configure SAML single sign-on with Active Directory Federation Services (AD FS) with instructions to integrate with ADFS and the page SAML single sign-on has been updated.

            Gabriel
            Atlassian Support

            Gabriel Muller (Inactive) added a comment - Hi all, Atlassian added the documentation  Configure SAML single sign-on with Active Directory Federation Services (AD FS) with instructions to integrate with ADFS and the page SAML single sign-on has been updated. Gabriel Atlassian Support
            André K. (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 439302 ]
            Michael Andreacchio made changes -
            Workflow Original: ACCESS Suggestion workflow [ 3156711 ] New: JAC Suggestion Workflow [ 3258592 ]
            Katherine Yabut made changes -
            Workflow Original: reviewflow [ 787509 ] New: ACCESS Suggestion workflow [ 3156711 ]
            André K. (Inactive) made changes -
            Attachment New: image001.png [ 328202 ]
            Attachment New: image003.png [ 328203 ]
            Attachment New: image004.png [ 328204 ]
            Attachment New: image005.png [ 328205 ]

            Michael Adam added a comment - - edited

            I have SSO working with AD FS 2.0

            Hopefully these update screenshots will help - it looks like things have changed since the post in Dec 2016.

            Enter on Atlassian side

            Identity provider Entity ID:

            http://adfs-server.domain.com/adfs/services/trust

            Identity provider SSO URL:

            https://adfs-server.domain.com/adfs/ls/

            Public x509 certificate:

            Export your Token-signing certificate as base 64 (how to get from AD FS 2.0 console: AD FS 2.0 -> Service -> Certificates)

             

            Enter on AD FS 2.0 side

            There are only 2 tabs that you need to populate with information - Identifiers and Endpoints but I've included screenshots for everything.

             

            Edit: looks like I can't upload new screenshots.

            In short, I used these values:

            Identifiers tab:

            Relying party identifier: SP Entity ID from sso config page on admin.atlassian.com

            (eg: https://auth.atlassian.com/saml/hex-string)

             

            Endpoints Tab: SAML Assertion Consumer Endpoint: SP Assertion Consumer Service URL from sso config page on admin.atlassian.com (eg: https://auth.atlassian.com/login/callback?connection=saml-hex-string)

             

            Advanced Tab: [default - SHA-265]

             

            Don't forget about the claims rules (see screenshot from Dec 2016 post)

             

             

             

             

             

             

             

            Claim rules are the same as the earlier post:

             

             

             

             

             

             

            Michael Adam added a comment - - edited I have SSO working with AD FS 2.0 Hopefully these update screenshots will help - it looks like things have changed since the post in Dec 2016. Enter on Atlassian side Identity provider Entity ID: http://adfs-server.domain.com/adfs/services/trust Identity provider SSO URL: https://adfs-server.domain.com/adfs/ls/ Public x509 certificate: Export your Token-signing certificate as base 64 (how to get from AD FS 2.0 console: AD FS 2.0 -> Service -> Certificates)   Enter on AD FS 2.0 side There are only 2 tabs that you need to populate with information - Identifiers and Endpoints but I've included screenshots for everything.   Edit: looks like I can't upload new screenshots. In short, I used these values: Identifiers tab: Relying party identifier: SP Entity ID from sso config page on admin.atlassian.com (eg: https://auth.atlassian.com/saml/hex-string)   Endpoints Tab: SAML Assertion Consumer Endpoint:  SP Assertion Consumer Service URL  from sso config page on admin.atlassian.com (eg:  https://auth.atlassian.com/login/callback?connection=saml-hex-string)   Advanced Tab: [default - SHA-265]   Don't forget about the claims rules (see screenshot from Dec 2016 post)               Claim rules are the same as the earlier post:            
            lingbo (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 387874 ]

            Saiful Islam added a comment -

            Ra maader cood kankemaager pola R a

            Saiful Islam added a comment - Ra maader cood kankemaager pola R a

            mchyzer2 added a comment -

            Once you register a domain for SSO, any user who self identifies (or has self identified) their email address as having that domain (exact domain, not subdomain), is now in your access management / SSO cohort...

            mchyzer2 added a comment - Once you register a domain for SSO, any user who self identifies (or has self identified) their email address as having that domain (exact domain, not subdomain), is now in your access management / SSO cohort...

              Unassigned Unassigned
              dwierzbicka Dobroslawa Wierzbicka (Inactive)
              Votes:
              473 Vote for this issue
              Watchers:
              380 Start watching this issue

                Created:
                Updated:
                Resolved: