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:
  • Login as "superuser" on Firefox.
  • Login as "mary" on Chrome.
  • On "superuser" side, go to Messages app, send a message to "mary".
    
    => Expected: "mary" receives that message in Pulse.
    => Actual: She doesn't.

• Steps to reproduce for publishing case:
  • Login as "mary" on Firefox.
  • Login as "john" on Chrome.
  • On "mary" side, go to Pages app, publish a page.
    
    => Expected: "john" receives that task in Pulse.
    => Actual: He doesn't.

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.