Admin privilege disappears after restart

[Shajimon Paremmal]

Hi,

I'm new to Jenkins and I'm using Jenkins on Windows.

I'm facing an admin privilege issue. Any help in resolving this will be highly appreciated.

These are the steps to reproduce the issue.;

The steps

1. Enable   security in Configure Global Security page.

2. Use Jenkins' own user database

3. Use Matrix-based security

4. Give read privilege to anonymous user

5. Create a user and give him all the permissions  

6. Save 

7. Create an account for the user just created.

8. Restart Jenkins server

9. Log in to Jenkins as the user just created.

The issue. The user can no longer configure the Jenkins or perform any admin tasks. Since there is only one user created, there is no way to configure the system other than turning the security off by editing the  config.xml.

Question - Do I need to follow any additional steps to make the user an admin? I cannot see the page for conferring this permission in the version 1.620 of Jenkins I have.

config.xml entries

The config.xml still shows that the user have all the necessary permissions, as shown below.

<authorizationStrategy class="hudson.security.GlobalMatrixAuthorizationStrategy">

    <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Create:Test</permission>

    <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Delete:Test</permission>

    <permission>com.cloudbees.plugins.credentials.CredentialsProvider.ManageDomains:Test</permission>

    <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Update:Test</permission>

    <permission>com.cloudbees.plugins.credentials.CredentialsProvider.View:Test</permission>

    <permission>hudson.model.Computer.Build:Test</permission>

    <permission>hudson.model.Computer.Configure:Test</permission>

    <permission>hudson.model.Computer.Connect:Test</permission>

    <permission>hudson.model.Computer.Create:Test</permission>

    <permission>hudson.model.Computer.Delete:Test</permission>

    <permission>hudson.model.Computer.Disconnect:Test</permission>

    <permission>hudson.model.Hudson.Administer:Test</permission>

    <permission>hudson.model.Hudson.ConfigureUpdateCenter:Test</permission>

    <permission>hudson.model.Hudson.Read:Test</permission>

    <permission>hudson.model.Hudson.Read:anonymous</permission>

    <permission>hudson.model.Hudson.RunScripts:Test</permission>

    <permission>hudson.model.Hudson.UploadPlugins:Test</permission>

    <permission>hudson.model.Item.Build:Test</permission>

    <permission>hudson.model.Item.Cancel:Test</permission>

    <permission>hudson.model.Item.Configure:Test</permission>

    <permission>hudson.model.Item.Create:Test</permission>

    <permission>hudson.model.Item.Delete:Test</permission>

    <permission>hudson.model.Item.Discover:Test</permission>

    <permission>hudson.model.Item.Read:Test</permission>

    <permission>hudson.model.Item.Workspace:Test</permission>

    <permission>hudson.model.Run.Delete:Test</permission>

    <permission>hudson.model.Run.Update:Test</permission>

    <permission>hudson.model.View.Configure:Test</permission>

    <permission>hudson.model.View.Create:Test</permission>

    <permission>hudson.model.View.Delete:Test</permission>

    <permission>hudson.model.View.Read:Test</permission>

  </authorizationStrategy>

Thanks in advance.

Shaji.

[Björn Pedersen]

Am Montag, 27. Juli 2015 13:15:49 UTC+2 schrieb Shajimon Paremmal:

Hi,

I'm new to Jenkins and I'm using Jenkins on Windows.

I'm facing an admin privilege issue. Any help in resolving this will be highly appreciated.

These are the steps to reproduce the issue.;

The steps

1. Enable   security in Configure Global Security page.

2. Use Jenkins' own user database

3. Use Matrix-based security

4. Give read privilege to anonymous user

5. Create a user and give him all the permissions  

6. Save 

7. Create an account for the user just created.

8. Restart Jenkins server

9. Log in to Jenkins as the user just created.

I would try to switch steps 7 before step 3.

Björn

[milki milk]

On Tuesday, July 28, 2015 at 1:16:27 AM UTC-7, Björn Pedersen wrote:

I would try to switch steps 7 before step 3.

Björn

Agreed. All required perms for the admin user should be set before the save step.

You also don't need to restart the server to apply perm changes.