When configuring JIRA service desk it appears that the baseURL is not updated in the service desk queues as the http:// appears to not be read from the baseURL value stored by JIRA in the config pages of the application.
As a consequence the service desk queues do not work as they make illegal calls to http://baseURL URLs instead of the expected https://
this triggers the CRSF engine and the page object fails.
how can I fix this
I am using apache to provide the SSL and proxying the requests back to JIRA
Hmm. It should be using a single base-url from the config, I'm not sure what the "variable" here is, unless it's something in the environment which it being inherited. Is that possible?
The other thought is maybe the proxy is doing something odd, like rewriting the urls. I'd want to test a service desk queue usage without going through the proxy to see what url gets used then, but I understand that might be quite difficult. Do you have access to the proxy settings?
If it's not an environment or proxy setting, then it sounds very much like a bug to me!
Yes, I mentioned the proxy because I got one wrong once and it did something similar to this with an add-on that grabbed data via REST. I'd got it proxying
Hopefully we'll get an answer from support soon!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs