• Role Strategy 3.1

      Role based access strategy plugin not working as intended. The project roles are not getting updated/assigned to the user.

      When we assign any project role or update the project role it does not reflect with the user access ie. User is still not able to access the new role / using old role .

      But when we made any change in role definition/permission or simply click apply/save in managed roles and then try to access with the user again, the changes comes into effect. That means every-time we give access to any user or update the permissions we need to do some updates in role permissions in order to enable the changes. 

          [JENKINS-61425] Role Based access strategy - not consistent

          Kapil Yadav added a comment -

          We accessing jenkins via Azure AD integration. 

          Kapil Yadav added a comment - We accessing jenkins via Azure AD integration. 

          Kapil Yadav added a comment -

          Kapil Yadav added a comment -

          Kapil Yadav added a comment -

          The conclusion is we needs to click apply/save in manage role , only after the changes in user role comes into effect.

          Kapil Yadav added a comment - The conclusion is we needs to click apply/save in manage role , only after the changes in user role comes into effect.

          Kapil Yadav added a comment -

          We have investigated more and found that the changes i am doing in "assigning role" tab are being written in config.xml of jenkins but somehow not getting reflecting in jenkins untill we apply changes in "manage roles" tab or load configurations from disk.

          Kapil Yadav added a comment - We have investigated more and found that the changes i am doing in "assigning role" tab are being written in config.xml of jenkins but somehow not getting reflecting in jenkins untill we apply changes in "manage roles" tab or load configurations from disk.

          Kapil Yadav added a comment -

          As per my observation this thing is happening for AD as well as local users.

          Kapil Yadav added a comment - As per my observation this thing is happening for AD as well as local users.

          Romano Nolux added a comment -

          We're experiencing the same issue with the latest version of the plugin with AD users.

          Luckily the workaround made things working as expected.

          Romano Nolux added a comment - We're experiencing the same issue with the latest version of the plugin with AD users. Luckily the workaround made things working as expected.

          Oleg Nenashev added a comment -

          Most likely it is caused by the caching problem fixed in 3.1. Please try updating to this version and report results if it does not help

          Oleg Nenashev added a comment - Most likely it is caused by the caching problem fixed in 3.1. Please try updating to this version and report results if it does not help

            oleg_nenashev Oleg Nenashev
            kapyad Kapil Yadav
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: