JIRA Startup Fails Due to 'java.lang.SecurityException Unable to locate a login configuration'
Symptoms
After installing the Subversion plugin for JIRA it no longer starts and the following exceptions appear in the logs:
2010-08-05 18:47:34,179 Thread-1 FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A fatal error occured during initialisation. JIRA has been locked.
java.lang.SecurityException: Unable to locate a login configuration
at com.sun.security.auth.login.ConfigFile.<init>(ConfigFile.java:93)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:30
Cause
The Subversion client SVNKit prefers negotiation authentication over basic authentication when configured over HTTP, so it is attempting to use it. For more information see Jetbrains' issue tracker.
Resolution
Append the following option to the JAVA_OPTS:
-Dsvnkit.http.methods=Basic
See Setting Properties and Options on Startup for details on how to configure startup options.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.