We're running a self-hosted installation of JIRA Software 7.3.5 on Server 2012 R2.
We ran all available Windows Updates on our JIRA server on Friday and upgraded to Java 8u144.
Today, all of our users are reporting that they can only log in by manually entering their passwords rather than using the credentials their browsers have cached.
Additionally, any attempt to log in with the 'Remember my login' check box populated fail.
We had similar problems in the past when we edited seraph-config.xml to increase cookie age but have since rolled back to the default value of 15780000.
Has anyone else reported anything similar? Any idea what we can do to remedy this?
Despite the JRE update, the JIRA service is still running in tomcat8.exe.x64. The stderr log file is showing that the Java Home is still pointing to the JIRA install directory with the JVM version of 1.8.0_102-b14.
Here's where I would start:
Thanks for getting back to me.
I had already tried restarting JIRA but that didn't fix the problem. This was happening in all browsers and for all users so it was a server-side problem. We don't use a proxy server.
I was able to remedy the problem by replacing our version of seraph-config.xml from a default install I ran on a test server and restarting JIRA.
I'm not sure what caused this to happen after this restart as the server has been rebooted several times with the old seraph-config.xml file in place, but service has been resumed.
You can close this ticket.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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