-
Bug
-
Resolution: Fixed
-
Major
-
None
-
jenkins:2.204.5 with role-strategy:2.16
-
-
Role Strategy 3.1
After addRole for a project role and assignRole to an LDAP user is takes 1 hour until the role can be used.
This can be an issue according to the cache implementation, and due to this issue we have to wait 1 hour for the Project Role to be effective.
We are using Jenkins: 2.204.5 with role-strategy:2.16 plugin.
*Update:
Even when the role is already there (e.g. for days) if you assign it to one user it will be visible on the management page in Jenkins - but the user still cannot use the role.
For the user it seems like he doesn't have the role, and after one hour it is working.
So therefore the cache might not be flushed correctly every time when the real change occurs.
Our guess is, that the cache flush done in https://github.com/jenkinsci/role-strategy-plugin/blob/master/src/main/java/com/michelin/cio/hudson/plugins/rolestrategy/RoleMap.java#L245 also needs to be done after an assignRole() and maybe in other methods also!
- is duplicated by
-
JENKINS-61425 Role Based access strategy - not consistent
- Resolved
-
JENKINS-62323 Role Edits Work But Jenkins Restart Required To Take Effect
- Closed
- relates to
-
JENKINS-61470 When I assign users to roles, changes are not applied until Jenkins restart
- Resolved