Can't login with JIRA User Management

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

Fisheye/Crucible connected with JIRA for User management.

After changing JIRA url to HTTPS, Fisheye/Crucible can't connect to JIRA anymore.

The following appears in the atlassian-fisheye-<date>.log:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 2013-11-05 12:24:59,259 ERROR [quartzScheduler_Worker-5 ] fisheye UserSynchroniserJob-execute - Error during the current user synchronisation com.cenqua.fisheye.user.AuthenticationException: Problem communicating with Crowd at com.cenqua.fisheye.user.crowd.CrowdAuth.listUserNames(CrowdAuth.java:514) at com.cenqua.fisheye.user.DefaultUserManager.synchroniseUsers(DefaultUserManager.java:697) at sun.reflect.GeneratedMethodAccessor323.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:309) ... Caused by: com.atlassian.crowd.exception.OperationFailedException: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty ... Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty ... Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty ... Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Cause

The trustAnchors parameter isn't setup in Fisheye/Crucible.

Resolution

  1. Add the following Java option into FISHEYE_OPTS environment variable:

    1 -Djavax.net.ssl.trustStore=path\to\jdk\lib\security\cacerts
  2. Restart Fisheye/Crucible

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.