-
Bug
-
Resolution: Fixed
-
High
-
5.6.0, 5.7.1, 5.7.2, 5.7.0
steps to reproduce
- Integrate bamboo with LDAP
- Configure the ldap caching so that the cache got refreshed every 20s for example
- Now create a group and associate a user to it
- The group will be created and the user associated as expected
- Now remove the user from the group and wait for the cache to run
Expected behaviour
Bamboo should remove the user from the group as well
Current behaviour
The user is still associated to the group and only a restart will remove the group association from the user. This only affects group membership as user details and creation of new groups get updated immediately. It appears this properties " LDAPGroupManagerReadOnly..groups_hasMembership and LDAPGroupManagerReadOnly..groups_getGroupsForUser" are ignored by the cache.
There is no error in the logs even when the "com.atlassian.user" class is set to DEBUG
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- was cloned as
-
BDEV-7165 Loading...
[BAM-15360] Ldap group membership not updated without a restart
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 101266 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1436988 ] | New: JAC Bug Workflow v3 [ 3384450 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Description |
Original:
*steps to reproduce*
# Integrate bamboo with LDAP # Configure the [ldap caching|https://confluence.atlassian.com/display/BAMBOO020/5.13.2.1+Configuring+the+Caching+of+your+LDAP+Repository] so that the cache got refreshed every 20s for example # Now create a group and associate a user to it # The group will be created and the user associated as expected # Now remove the user from the group and wait for the cache to run *Expected behaviour* Bamboo should remove the user from the group as well *Current behaviour* The user is still associated to the group and only a restart will remove the group association from the user. This only affects group membership as user details and creation of new groups get updated immediately. It appears this properties " LDAPGroupManagerReadOnly.*.groups_hasMembership and LDAPGroupManagerReadOnly.*.groups_getGroupsForUser" are ignored by the cache. There is no error in the logs even when the "com.atlassian.user" class is set to DEBUG |
New:
*steps to reproduce*
# Integrate bamboo with LDAP # Configure the [ldap caching|https://confluence.atlassian.com/display/BAMBOO/Configuring+the+caching+of+your+LDAP+repository] so that the cache got refreshed every 20s for example # Now create a group and associate a user to it # The group will be created and the user associated as expected # Now remove the user from the group and wait for the cache to run *Expected behaviour* Bamboo should remove the user from the group as well *Current behaviour* The user is still associated to the group and only a restart will remove the group association from the user. This only affects group membership as user details and creation of new groups get updated immediately. It appears this properties " LDAPGroupManagerReadOnly.*.groups_hasMembership and LDAPGroupManagerReadOnly.*.groups_getGroupsForUser" are ignored by the cache. There is no error in the logs even when the "com.atlassian.user" class is set to DEBUG |
| Workflow | Original: Bamboo Workflow 2016 v1 [ 1420606 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1436988 ] |
| Workflow | Original: Bamboo Workflow 2014 v2 [ 785884 ] | New: Bamboo Workflow 2016 v1 [ 1420606 ] |
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 101266 ] | New: This issue links to "Page (Atlassian Documentation)" [ 101266 ] |
| Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 101266 ] |