CORS FAiled Warning in Jira

[Deepak Mammen]

Receiving below Warning in Jira

2020-07-02 04:29:28,641 http-nio-8080-exec-10 WARN  /rest/webResources/1.0/resources [c.a.p.r.c.security.jersey.XsrfResourceFilter] Additional XSRF checks failed for request: https://jira.junipercloud.net/it/rest/webResources/1.0/resources , origin: http://jira.junipercloud.net , referrer: http://jira.junipercloud.net/it/secure/Dashboard.jspa , credentials in request: false , allowed via CORS: false

Base Url is https://ira.junipercloud.net/it/

Why did XSRF checks fail?

What changes needs to be done to fix this?

[Italo Qualisoni [e-Core]]

In the logs you can see that the request is using https but the origin is on http

This looks like a miss configuration in your server.xml file.

Have you perform some recent upgrade? I'm asking because server.xml file is usually overwritten during the upgrade process.

If you are running behind a proxy, can you check if the Connector attribute under your server.xml contains the below attributes:

proxyName="jira.junipercloud.net" proxyPort="443" scheme="https" secure="true"

See below a Confluence KB that describe the same issue:

https://confluence.atlassian.com/confkb/after-upgrading-confluence-you-are-unable-to-create-new-pages-or-spaces-785457379.html

[Deepak Mammen]

Thanks ,

But I checked server.xml multiple types.

We set it correctly. 

Is there any other place, where I can check where origin and referrer is set.

Why it says origin is http

Thanks,

Deepak

[Italo Qualisoni [e-Core]]

Hi Deepak,

You can find more details here:

https://confluence.atlassian.com/kb/cross-site-request-forgery-csrf-protection-changes-in-atlassian-rest-779294918.html

In case you modify the server.xml you will need to restart the application in order to apply the changes.

When did this start to happen? 

[Deepak Mammen]

We started getting it recently.

Not sure the exact reason

[Italo Qualisoni [e-Core]]

I think if you checked the server.xml file and it's correct you should look into Atlassian support channel. Another good practice is redirect http traffic to https on your proxy, maybe it's allowing http as well?

Also I work as consultant at e-Core and we have the expertise to assist you troubleshoot this issue, if that interest  please contact me at italo.qualisoni@e-core.com and I'll redirect your request internally.

[Italo Qualisoni [e-Core]]

Hi @Deepak Mammen ,

How is your troubleshooting going? Any progress with this issue?

[Deepak Mammen]

No progress,

[Eric0929]

you may try to add  http://jira.junipercloud.net to the Allowlist. 
IF that's OK. means someone use not https to access.