Security permissions wiped after server restart

[Chris Parr]

Hi,

Really frustrating problem here.

I've posted on stackoverflow (here), but thought I'd cross post here as there was no solution given. I'm thinking this must be a bug.

1. downloaded rpm jenkins-1.590-1.1.noarch.rpm from the jenkins site
2. installed on redhat
3. Can create jobs and everything runs fine
4. Enabled jenkins own DB security with matrix based permissions
5. Added myself as a user will all permissions
6. Restarted server
7. Completed sign up of my user account
   
8. Everything works as expected. All permissions are enabled so I can do what I want.
9. Restart the server
10. Log back in
11. All my access permissions are gone and I have to disable security to do anything (remove config.xml and delete user dir).
12. I can go through the process above again, but the permissions don't stick.
13. I've upgraded to the latest version but the problem persists.

Does anyone have any ideas, or at least seen this problem so I know I'm not the only one.

This must be a bug.

Cheers

[Chris Parr]

Have raised a bug in Jenking Jira: JENKINS-25842

[Niksan]

I've see the exact same, you're not alone, I thought it fully wiped out my accounts but I didn't re-enable Jenkins internal database so my post (or the second part of it at least) is irrelevant.

https://groups.google.com/forum/#!topic/jenkinsci-users/E42NFkiHCPM

[Scribe]

Thanks Niksan,

Glad I'm not the only one. I'll check the status of the ticket tomorrow. Hopefully someone will acknowledge the issue.

Cheers 

 

[Niksan]

The annoying thing is, the permissions still exist in config.xml, it's almost as if Jenkins is just not reading them in at all when rebooting the server.

[Scribe]

I have a work around:

1. Restrict usernames to lower case

2. After setting up security and before the server restart, save the 'configure system' page even if no changes have been made - not sure if this is required (I was following a suggestion by someone more in the know than I), but it won't hurt.

User permissions now persist after restart on my instance. 

I have updated the JIRA ticket I created.

Regards

Chris