|
One may accidentally set up security realm / authorization in such a way that you may no longer able to reconfigure Jenkins. When this happens, you can fix this by the following steps:
When Jenkins comes back, it's in the unsecured mode where everyone gets full access to the system. If this is still not working, trying renaming or deleting config.xml. |
Disable security
Skip to end of metadata
Go to start of metadata
Comments (5)
Nov 02, 2011
Steven Merrill says:
Actually, in current versions, you should replace whatever you have in your conf...Actually, in current versions, you should replace whatever you have in your config.xml with the following:
Jul 20, 2012
philihp busby says:
Yes, that is important. I did the above and was being forwarded to http://l...Yes, that is important. I did the above and was being forwarded to http://localhost:8080/securityRealm/commenceLogin?from=%2F, with a screen that read
StatusCode:404
Exception:
Stacktrace:
(none)
Status Code: 404
Exception:
Stacktrace:
(none)
This was fixed by using the options Steve Merrill suggested.
Nov 15, 2013
Atuhaire Edwin says:
I am new to Jenkins and need assistance in gaining access to my Jenkins installa...I am new to Jenkins and need assistance in gaining access to my Jenkins installation.
I successfully managed to lock myself out on the Jenkins ver. 1.539 and i am unable to gain access to it.
i had set up my security realm to use the Jenkins database.
The config.xml file seems to have been excluded from this release and as such am unable to edit it.
How do i gain access?
Sep 19, 2014
Antony Sakkariaz says:
I also locked myself out while configuring security. Steven Merrill's suggestio...I also locked myself out while configuring security.
Steven Merrill's suggestion worked for me.
However, finding the config.xml file was difficult, because I installed Jenkins 1.580 using theDebian package. In my case, the variable $JENKINS_HOME was empty.
After some search, I found the file /etc/default/jenkins showed that jenkins home is /var/lib/jenkins/.
I found the config.xml there, changed it as per Steven Merrill suggestion, and restarted jenkins daemon by using the command "sudo service jenkins restart".
This fixed the problem.
Jan 31
Alexander Kunin says:
If jenkins is installed under servlet container on Windows machine, config.xml c...If jenkins is installed under servlet container on Windows machine, config.xml can be found at c:\Windows\System32\config\systemprofile\.jenkins\
Add Comment