-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Saigon 44
-
8
Steps to reproduce
Assuming we have 2 LDAP accounts: "mary" belongs to group "travel-demo-editors", and "john" belongs to "travel-demo-publishers".
- Steps to reproduce for Messages app case:
- Steps to reproduce for publishing case:
Description
The pulse badge doesn't get updated, when using an ExternalUserManager e.g. LDAPUserManager .
You have to explicitly click into the pulse-tab, to refresh the pulse. Even reload is not enough to refresh the badge.
Normally, in MessagesManagerImpl#sendGroupMessage the message is pushed into the pulse of the User. The relevant users are identified by DelegatingUserManager#getUsersWithGroup - but within the method delegateUntilSupported - after the first UserManager returns users (SystemUserManager), the other UserManagers don't get called.
Solution
- Provide a default implementation for ExternalUserManager#getUsersWithGroup.
- Add new implementation for DelegatingUserManager#getUsersWithGroup and DelegatingUserManager#getUsersWithRole to collect users from all user managers.
- is causing
-
MAGNOLIA-6906 Avoid calling #getAllUser several times when resolving users with group transitively in ExternalUserManger
- Closed
- relates to
-
MGNLCI-12 Pulse icon does not show number of new items
- Closed