I created a test JIRA environment doing the below
1. Took a snapshot of my database server and launched it
2. Took a snapshot of my existing production JIRA server and launched it
3. Replicated my environment network/secgroups etc.
I am able reach my test environment on browser but when I try and log-in I am caught in a loop
I checked the atlassian-jira-security.log and the log-in authentication shows as successful
2019-08-21 12:10:20,645 http-nio-8080-exec-9 user1 730x67x1 - x.x.x.x /rest/gadget/1.0/login The user 'user1' has PASSED authentication.
The atlassian-jira.log however is showing the below error
2019-08-21 12:13:31,544 http-nio-8080-exec-23 WARN anonymous 733x85x1 - x.x.x.x /rest/analytics/1.0/publish/bulk [c.a.p.r.c.security.jersey.XsrfResourceFilter] Additional XSRF checks failed for request: https://jira.productionserver.blabla.com , origin: null , referrer: http://jiratestserver:8080/secure/Dashboard.jspa , credentials in request: false , allowed via CORS: false
Looks like the test server is referring the login to the prod server? and its failing with this CORS setting? anyone know what I should do?
Two things,
Hi DPK,
Thanks for the reply.
Yes to both questions but its still failing unfortunately
Thanks,
Deirdre
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Look at this and validate again - https://confluence.atlassian.com/confkb/after-upgrading-confluence-you-are-unable-to-create-new-pages-or-spaces-785457379.html
Also don't forget to restart confluence after changing your `server.xml`.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay so my server.xml file on my test server shows
<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="jira.productionenvironment.com" proxyPort="443"/>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You need to remove
scheme="https" proxyName="jira.productionenvironment.com" proxyPort="443"
This tell Jira that your site url is "https://jira.productionenvironment.com", which is not correct for test instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I edited it to my new test server name for the ProxyName and I changed the port and it still doesnt work after a restart
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.