Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-6629

User Directory test fails with "The validated object is null" when "Enable aliasing" is selected in FishEye

    XMLWordPrintable

Details

    • Bug
    • Resolution: Tracked Elsewhere
    • Low
    • N/A
    • 4.1.1
    • None
    • None

    Description

      Summary

      When "Enable aliasing" is enabled in Crowd, the connection to Crowd from FishEye fails and users are not able to login.

      This problem is caused by CWD-4308, which has been resolved in Crowd 2.8.4.

      Environment

      • Crowd prior to 2.8.4

      Steps to Reproduce

      1. Connect FishEye to Crowd
      2. "Enable aliasing" in the Crowd Options tab

      Expected Results

      FishEye can successfully connect to Crowd.

      Actual Results

      The following is shown in the FishEye user interface in the Configure Atlassian Crowd Server

      Connection test failed. Response from the server:
      Error from Crowd server propagated to here via REST API (check the Crowd server logs for details): The validated object is null
      

      The below exception is thrown in the atlassian-fisheye-YYYY-MM-DD.log file:

      ERROR [qtp1096485705-494 ] com.atlassian.crowd.embedded.admin.ConfigurationController ConfigurationController-handleSubmit - Confi
      guration test failed for user directory: [ Crowd Server], type: [ CROWD ]
      com.atlassian.crowd.exception.runtime.OperationFailedException: Error from Crowd server propagated to here via REST API (check the Crowd server logs for details): The validated object is null
              at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.testConnection(CrowdDirectoryServiceImpl.java:78) [embedded-crowd-core-2.8.5-m1.jar:?]
              at com.atlassian.fecru.user.crowd.DelegatingCrowdDirectoryService.testConnection(DelegatingCrowdDirectoryService.java:29) [fisheye.jar:?]
      ...
      Caused by: com.atlassian.crowd.exception.OperationFailedException: Error from Crowd server propagated to here via REST API (check the Crowd server logs for details): The validated object is null
              at com.atlassian.crowd.integration.rest.service.RestCrowdClient.handleCommonExceptions(RestCrowdClient.java:1556) [crowd-integration-client-rest-2.8.5-m1.jar:?]
              at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:590) [crowd-integration-client-rest-2.8.5-m1.jar:?]
              at com.atlassian.crowd.integration.rest.service.RestCrowdClient.testConnection(RestCrowdClient.java:574) [crowd-integration-client-rest-2.8.5-m1.jar:?]
      ...
      Caused by: com.atlassian.crowd.integration.rest.service.CrowdRestException: The validated object is null
              at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.throwError(RestExecutor.java:656) [crowd-integration-client-rest-2.8.5-m1.jar:?]
              at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:485) [crowd-integration-client-rest-2.8.5-m1.jar:?]
              at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:586) [crowd-integration-client-rest-2.8.5-m1.jar:?]
      

      The following can be found in the Crowd log files:

      http-bio-8095-exec-12 ERROR [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: The validate
      d object is null
      java.lang.NullPointerException: The validated object is null
              at org.apache.commons.lang3.Validate.notNull(Validate.java:222)
              at org.apache.commons.lang3.Validate.notNull(Validate.java:203)
              at com.atlassian.crowd.manager.application.AliasManagerImpl.findUsernameByAlias(AliasManagerImpl.java:35)
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ccurti Caterina Curti
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: