Uploaded image for project: 'SAML for Atlassian Data Center'
  1. SAML for Atlassian Data Center
  2. SAMLDC-37

If the authenticating user comes from a remote directory, and the directory is inaccessible the user will see a 'We can't log you in right now error'

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • 2.0.2
    • None

      When authenticating using SAML, if the user logging in comes from a remote directory (for example an LDAP or Crowd directory), and the directory is can't be reach by the application, the user will be unable to log in, and see the 'We can't log you in right now message'.

      The logs will say:

      com.atlassian.plugins.authentication.impl.web.usercontext.AuthenticationFailedException: Received SAML assertion for user UserFromRemote, but the user doesn't exist in the product
              at com.atlassian.plugins.authentication.impl.web.usercontext.impl.SalPrincipalResolver.resolvePrincipal(SalPrincipalResolver.java:34)
              at com.atlassian.plugins.authentication.impl.web.saml.SamlConsumerServlet.doPost(SamlConsumerServlet.java:92)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
      

      Expected:

      • the user should be able to log in using the user details cached in the product if available

          Form Name

            [SAMLDC-37] If the authenticating user comes from a remote directory, and the directory is inaccessible the user will see a 'We can't log you in right now error'

            This bug is affecting our Confluence and Bitbucket instances. We have vulnerability/security report which needs Jira point upgrade at least once a month and on top of it we have some maintenance activity every month and because of this Confluence and Bitbucket are inaccessible to clients which blocks them from releases. This impact our business heavily.

            So I request you to please raise its priority and let us know by when this can be fixed.

            Nikita Garg added a comment - This bug is affecting our Confluence and Bitbucket instances. We have vulnerability/security report which needs Jira point upgrade at least once a month and on top of it we have some maintenance activity every month and because of this Confluence and Bitbucket are inaccessible to clients which blocks them from releases. This impact our business heavily. So I request you to please raise its priority and let us know by when this can be fixed.

              Unassigned Unassigned
              lpater Lukasz Pater
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: