Unable to add Crowd as directory in JIRA with Outbound Proxy in between
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Problem
With Outbound Proxy is in between of JIRA and Crowd, trying to integrate using the Domain would not be possible but integrating it directly (e.g. IP Address) is possible.
In the atlassian-jira.log the following error is showing:
2018-09-26 10:12:46,371 http-bio-8091-exec-1 WARN user1 612x758x1 116hemz 195.212.199.56,10.12.56.125,127.0.0.1 /plugins/servlet/embedded-crowd/configure/crowd/ [org.springframework.beans.TypeConverterDelegate] PropertyEditor [com.sun.beans.editors.EnumEditor] found through deprecated global PropertyEditorManager fallback - consider using a more isolated form of registration, e.g. on the BeanWrapper/BeanFactory!
2018-09-26 10:12:51,928 http-bio-8091-exec-1 ERROR user1 612x758x1 116hemz 195.212.199.56,10.12.56.125,127.0.0.1 /plugins/servlet/embedded-crowd/configure/crowd/ [crowd.embedded.admin.ConfigurationController] Configuration test failed for user directory: [ Crowd Server], type: [ CROWD ]
com.atlassian.crowd.exception.runtime.OperationFailedException: org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 5000 ms
at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.testConnection(CrowdDirectoryServiceImpl.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129)
at com.sun.proxy.$Proxy204.testConnection(Unknown Source) <+3> (NativeMethodAccessorImpl.java:57) (DelegatingMethodAccessorImpl.java:43)Diagnosis
Environment
- JIRA and Crowd are configured with Outbound Proxy in between.
Diagnostic Steps
- Check if the JVM argument in "Configure an outbound proxy for use in Jira server" is already set
- Check that each server is allowing the connection.
Cause
It seems that for Crowd Plugin, it has its own JVM Flag to use rather than the flag mentioned in the KB above.
Workaround
Use the following JVM Argument to set the Outbound Proxy details:
-Dcrowd.property.http.proxy.host
-Dcrowd.property.http.proxy.portFind out how easy, scalable and effective it can be with Crowd!
See centralized user management.