Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-592

Logging out of Atlassian account does not log out of SAML provider

XMLWordPrintable

    • 104
    • Hide

      Update December 17, 2024

      Thank you for all of your feedback, we are now actively working on this feature request. We understand the importance of it, and we are prioritizing it accordingly. Please stay tuned for updates on a targeted launch date, we will have that for you in the new year. in the meantime, please do continue to leave your feedback here.

      Show
      Update December 17, 2024 Thank you for all of your feedback, we are now actively working on this feature request. We understand the importance of it, and we are prioritizing it accordingly. Please stay tuned for updates on a targeted launch date, we will have that for you in the new year. in the meantime, please do continue to leave your feedback here.

    • 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.

      If a user is logged in to an external Identity provider (SAML), when they log out of Atlassian account they do not get logged out of the IdP.

      This can mean that if a user logs out of an Atlassian product to then try and log in with a different email on the same domain, the login will fail as Atlassian receives a different email from the IdP.

      Many SAML providers support 'single sign out' which would solve this issue if integrated.

            [ACCESS-592] Logging out of Atlassian account does not log out of SAML provider

            l.liesse added a comment -

            Hello, is it ok now?

            l.liesse added a comment - Hello, is it ok now?

            Dimitri Golyshev added a comment -

            9296fec66f8a, thank you, please be sure to update us. Appreciate your help!

            Dimitri Golyshev added a comment - 9296fec66f8a , thank you, please be sure to update us. Appreciate your help!

            Reda Zerrad added a comment -

            Hi 4bcd3952f2c7 thanks for the context, we understand the urgency and we apologies for any confusion our internal fiscal years are a bit different , I can confirm that we are actively working on a solution and targeting end of June for release.

            Reda Zerrad added a comment - Hi 4bcd3952f2c7 thanks for the context, we understand the urgency and we apologies for any confusion our internal fiscal years are a bit different , I can confirm that we are actively working on a solution and targeting end of June for release.

            Dimitri Golyshev added a comment -

            Thank you 9296fec66f8a and eee30c920d0f for responding and updating us in a timely manner.

             

            This issue needs to be addressed immediately. Waiting until the end of the year is too long, given the impact this issue is having.

            Since transitioning from ServiceNow to JSM last week, we've been dealing with a major flaw: tickets are being created under the wrong accounts, causing incorrect users to receive constant notifications. This is creating confusion, unnecessary disruptions, and a significant operational headache.

            This fix cannot be delayed. I strongly urge you to escalate its priority and push for a sooner resolution. I’m certain other teams and organizations are facing the same issue, and every day this persists, the problem compounds.

             

            Thank you!

            Dimitri Golyshev added a comment - Thank you 9296fec66f8a and eee30c920d0f for responding and updating us in a timely manner.   This issue needs to be addressed immediately. Waiting until the end of the year is too long, given the impact this issue is having. Since transitioning from ServiceNow to JSM last week, we've been dealing with a major flaw: tickets are being created under the wrong accounts, causing incorrect users to receive constant notifications. This is creating confusion, unnecessary disruptions, and a significant operational headache. This fix cannot be delayed. I strongly urge you to escalate its priority and push for a sooner resolution. I’m certain other teams and organizations are facing the same issue, and every day this persists, the problem compounds.   Thank you!

            Reda Zerrad added a comment - - edited

            I confirm that we are on track to deliver this by end FY25 Q4

            Reda Zerrad added a comment - - edited I confirm that we are on track to deliver this by end FY25 Q4

            Srivatsa Manjunath added a comment - - edited

            686b6de14f53 9296fec66f8a Please post an update. We are on track for FY25 Q4 delivery.

            Srivatsa Manjunath added a comment - - edited 686b6de14f53 9296fec66f8a Please post an update. We are on track for FY25 Q4 delivery.

            Moses Thomas added a comment -

            Hi, I see that assignee is inactive we are still waiting for solution ASAP

            Moses Thomas added a comment - Hi, I see that assignee is inactive we are still waiting for solution ASAP

            Dimitri Golyshev added a comment -

            Hello d056dd6d7b90, any update on this issue? This poses as a big security risk for our organization of 30k+ users. I do not see any updates on a launch date on any of these tickets and on Atlassian Administration. I do also notice that linked ticket ACCESS-1655 has nobody assigned to it. We hope to hear from your team soon, thank you.

            Dimitri Golyshev added a comment - Hello d056dd6d7b90 , any update on this issue? This poses as a big security risk for our organization of 30k+ users. I do not see any updates on a launch date on any of these tickets and on Atlassian Administration. I do also notice that linked ticket ACCESS-1655 has nobody assigned to it. We hope to hear from your team soon, thank you.

            l.liesse added a comment -

            it's just to call url disconnet/SAML provider after log off!

            l.liesse added a comment - it's just to call url disconnet/SAML provider after log off!

            l.liesse added a comment -

            could you correct it ASAP!!!

            l.liesse added a comment - could you correct it ASAP!!!

              9296fec66f8a Reda Zerrad
              jevans@atlassian.com Jeremy Evans
              Votes:
              155 Vote for this issue
              Watchers:
              136 Start watching this issue

                Created:
                Updated: