JIRA should catch Crowd failures gracefully

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Won't Do
    • Component/s: None
    • None

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      When JIRA is connected with Crowd and Crowd fails during the time that a user is using Confluence, the following stacktrace is displayed : 

      com.atlassian.crowd.exception.runtime.CommunicationException
	at com.atlassian.crowd.embedded.core.CrowdServiceImpl.convertOperationFailedException(CrowdServiceImpl.java:866)
	at com.atlassian.crowd.embedded.core.CrowdServiceImpl.authenticate(CrowdServiceImpl.java:79)
	at com.atlassian.crowd.embedded.core.DelegatingCrowdService.authenticate(DelegatingCrowdService.java:35)
	at com.atlassian.crowd.embedded.core.FilteredCrowdServiceImpl.authenticate(FilteredCrowdServiceImpl.java:51)
	at com.atlassian.jira.security.login.LoginManagerImpl$InternalStaticDependencies.authenticate(LoginManagerImpl.java:415)

      Steps to reproduce :

      • Integrate JIRA with Crowd
      • Login to JIRA with a user from Crowd
      • Shutdown Crowd
      • Try to perform some action on JIRA.

      JIRA should catch the Crowd exception in a better way and communicate to the user that the Crowd server is no longer accessible.

      Diagnosis and Resolution

      Please follow the diagnosis and resolution steps from the knowledge base article JIRA drops LDAP configuration - java.naming.provider.url property does not contain a URL.

            Assignee:
            Unassigned
            Reporter:
            Ruchi Tandon (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: