- Q: how to solve this? A: mostly by taking notes
- Q: which security model do I use? A: “Role-Based Strategy“
general approach:
- fix a few bits within config.xml and another few bits within your Jenkins web GUI
- for editing config.xml stop your Jenkins of course
- create a new (privileged) user account, and change your main account’s password through this new privileged user account
now in detail:
- stop your Jenkins
- within $JENKINS_HOME/config.xml change a few values for the time being:
- toggle
<useSecurity>true</useSecurity>to<useSecurity>false</useSecurity> - toggle
<disableSignup>true</disableSignup>to<disableSignup>false</disableSignup> - start your Jenkins again
- sign up a new user account (next time your main account is in trouble, use this one!)
- stop your Jenkins again
- add another
<sid>...</sid>entry for your new user account - …
- toggle your security entries shown above back to their original values
- start your Jenkins again
- change the troubled account’s password Jenkins-wise
- everything should be fine again