nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bonfire over https

Jim McCaskey

Hi there,

I have Bonfire installed in my Jira 4.3.4 instance and have got the license set up. I have been able to install the plugin in both Chrome and Firefox. However, neither of them will let me connect. The both give me an error that says

The URL

https://<server>/jira/rest/auth/latest/session

responded with a status code of 500

The only think I can think of is maybe this is a problem running Bonfire over https? Any other thoughts?

-Jim

Accepted answers

All comments

Penny Wyatt (On Leave to July 2021)

What do you see when you hit that URL directly in the browser? What errors are in the JIRA logs?

Jim McCaskey

Well I get the below stack trace, not that this forum lets you post the whole thing...

2011-07-29 10:08:20,621 http-8080-6 ERROR jmccaske 608x361x1 1fhe003 172.16.5.60,127.0.0.1 /rest/auth/latest/session [jira.rest.exception.ExceptionInterceptor] Returning internal server error in response
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor422.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

Penny Wyatt (On Leave to July 2021)

Hmm, if there's anything useful in the stack trace, I guess it's further down than that. Could you please paste the whole thing into http://pastie.org/ and share the link?

Jim McCaskey

Here you go:

http://pastie.org/2290309

Penny Wyatt (On Leave to July 2021)

Thanks for the full details. The error seems to be deep down in the Crowd layer of JIRA (and unrelated to HTTPS):

Caused by: java.lang.ClassCastException: com.sun.jndi.ldap.LdapCtx cannot be cast to org.springframework.ldap.core.DirContextAdapter

It looks like in your environment, Bonfire may be encountering this bug - https://jira.atlassian.com/browse/CWD-2414

Could you please try adding the following to JVM_REQUIRED_ARGS in bin\setenv.sh (or setenv.bat if you're on Windows):

-Datlassian.org.osgi.framework.bootdelegation=sun.*, com.sun.*, org.springframework.ldap.core.*

Then restart JIRA and see if it makes a difference?

-------------------------------------

Summary of results:

This is a JIRA bug that can affect customers on JIRA 4.3.x and earlier when using LDAP.
The bug is fixed in JIRA 4.4.
In the meantime, adding the argument above to JVM_REQUIRED_ARGS (not JVM_SUPPORT_RECOMMENDED_ARGS as I originally incorrectly advised) should act as a workaround.

Jim McCaskey

Ummm.... I don't use Crowd.

Penny Wyatt (On Leave to July 2021)

JIRA 4.3 comes with an embedded version of Crowd that it uses to manage its users and groups. You don't see it but it's there :-)

Jim McCaskey

Sneeky...

I tried setting this:

JVM_SUPPORT_RECOMMENDED_ARGS="-Datlassian.org.osgi.framework.bootdelegation=sun.*, com.sun.*, org.springframework.ldap.core.*"

It threw this on startup:

http://pastie.org/2290504

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

capture-for-jira