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

When IdP has a configuration problem, loading a managed account from directory gives a misleading error

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

      Issue Summary

      When the Identity Provider configuration has a configuration problem, caused by a change in permissions from the IdP Admin or perhaps the IdP is not properly set, when you try to open a synced managed account with the IdP the page displays "Something Went Wrong" instead of the user information.

      You won't notice there is an issue with the IdP until you review the IdP configuration in the Security Tab.

      Steps to Reproduce

      1. Have an IdP connected to your Atlassian org.
      2. Sync accounts and groups.
      3. Break the connectivity, maybe by changing the credentials of the IdP admin.
      4. Try to access a managed account synced with the IdP from Directory > Managed Accounts

      Expected Results

      • Account page loads with the latest synced information of the user and a highlighted message displaying there is an issue with the IdP configuration.

      Actual Results

      • The account page tries to load user information but at the end gives a "Something went wrong".

      Workaround

      The fix is to go directly to Security > Identity Providers and fix the configuration of the IdP. However, for a less experienced org admin, this could take time to figure out.

          Form Name

            [ACCESS-1601] When IdP has a configuration problem, loading a managed account from directory gives a misleading error

            No work has yet been logged on this issue.

              Unassigned Unassigned
              b9aede878664 Alonso Jimenez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated: