Can't login with JIRA User Management
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:
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-emptyCause
The trustAnchors parameter isn't setup in Fisheye/Crucible.
Resolution
Add the following Java option into FISHEYE_OPTS environment variable:
-Djavax.net.ssl.trustStore=path\to\jdk\lib\security\cacerts- Restart Fisheye/Crucible
Last modified on Jul 31, 2018
Powered by Confluence and Scroll Viewport.