1

I'm on Jenkins 2.235.2 and without any user input every once in a while (like half an hour at most) the security settings just changes itself back to "Delegate to servlet container" instead of "Jenkins' own user database". I can change it back and the user database I have set up is untouched. Other settings are not magically changing themselves either, just this one in particular. What gives???

the setting in question

K. M
  • 867
  • 1
  • 8
  • 17

2 Answers2

1

I ran into this exact issue as well using the google-login plugin, and for me the configuration-as-code plugin was reverting the setting. I'm using the Jenkins helm chart and by default the chart uses that instead of the XML files. You can add the security realm setting to the JCasC securityRealm if that's how you are deploying Jenkins. Alternatively you can enable using XML and disable JCasC.

bowlesns
  • 36
  • 5
0

M

While running jenkins in containers it is better to use persistant volume to save it's configuration. Also it's better to rebuild jenkins image after changing parameters in separate config files. This behavior could happen if you are using CM tools like ansible, puppet etc. or you are using jenkins configuration as code.

Dmitriy Tarasevich
  • 1,082
  • 5
  • 6
  • not sure I understand entirely. all of my configuration gets saved just fine except this one particular setting. i am of course using a persistent volume, in fact when i switch back to "user database" all my configured users are still all there! – K. M Jul 27 '20 at 18:45
  • Jenkins doesn't change it's configurations itself. Must be something, that is changing your config, or reverting your changes back to previous stage. – Dmitriy Tarasevich Jul 28 '20 at 07:13