# Admin account locked out after editing Global Security

**URL:** <https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684>\
**Category:** Using Jenkins\
**Tags:** question\
**Created:** [March 2, 2022, 1:08am UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684 "2022-03-02T01:08:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dchau](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@dchau](https://community.jenkins.io/u/dchau)\
**Post date:** [March 2, 2022, 1:08am UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684/1 "2022-03-02T01:08:11Z")

</div>

We have 2 jenkins k8s containers setup for production and test: jenkins and jenkins-tst. I noticed that jenkins-tst did not have the option to add users. I tried editing Global Security to match what is set on the production jenkins and then the admin password stopped working.

I’ve edited config.xml to reset the password using [Disable Access Control](https://www.jenkins.io/doc/book/security/access-control/disable/#using-config-xml) but it still prompts for password.

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [March 2, 2022, 2:39am UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684/2 "2022-03-02T02:39:40Z")

</div>

did you startart the pod after making the change? there should be 0 security when access control is disabled.

---

<div class="post-metadata">

**Author:** ![dchau](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@dchau](https://community.jenkins.io/u/dchau)\
**Post date:** [March 2, 2022, 3:47am UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684/3 "2022-03-02T03:47:56Z")

</div>

Yes, it has been restarted.

---

<div class="post-metadata">

**Author:** ![dchau](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@dchau](https://community.jenkins.io/u/dchau)\
**Post date:** [March 2, 2022, 7:46am UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684/4 "2022-03-02T07:46:18Z")

</div>

I logged into the new jenkins container and double checked **/var/jenkins\_config/config.xml** has

> useSecurity\>false\</useSecurity

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [March 3, 2022, 7:40am UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684/5 "2022-03-03T07:40:24Z")

</div>

Did you do step 5 as well? With 4 and 5 complete there should be no auth enabled at all, so I don’t know why your seing a login screen.

Maybe your editing a backup or the wrong server?

---

<div class="post-metadata">

**Author:** ![dchau](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@dchau](https://community.jenkins.io/u/dchau)\
**Post date:** [March 3, 2022, 4:19pm UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684/6 "2022-03-03T16:19:38Z")

</div>

I’ve reran the reset instructions with the same results. Here is a pastebin of the config.xml [https://pastebin.com/hSM5YuhK](https://pastebin.com/hSM5YuhK) . I knows it’s correct server because the config file changed after editing and container the url is unreachable when killing container.

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [March 3, 2022, 6:12pm UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684/7 "2022-03-03T18:12:27Z")

</div>

I’m really not sure what to tell you, i think we need more information. “I made the change as per the docs and it didn’t work” isn’t a lot to go on. With security disabled, it should work as everyone has all access, and never ask you for passwords. My guess is something else is going on, maybe the login screen is outside of jenkins, or a weird plugin is doing something special.

---

<div class="post-metadata">

**Author:** ![dchau](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@dchau](https://community.jenkins.io/u/dchau)\
**Post date:** [March 5, 2022, 8:56pm UTC](https://community.jenkins.io/t/admin-account-locked-out-after-editing-global-security/1684/8 "2022-03-05T20:56:29Z")

</div>

Yes! Got it working!

I found another config.xml in the container under /var/jenkins\_home/config.xml. The one I edited with kubectl was under /var/jenkins\_config/config.xml
