I just spent a fair amount of time tracking down this issue in our Crowd instance.
.
In my experience this problem is a function of being a Crowd "platform administrator" versus being a "delegated administrator" for a particular Crowd group. At least in Crowd 5.1.0, the users in a Crowd group are NOT subject to pagination for a platform administrator. But for someone who is not a platform admin, and only has access to manage specific groups, pages are used to display the group members. If the non-admin attempts to add someone NOT on the current page, the GUI will appear to "add" the user. If the user wasn't already in the group, the Crowd audit log will accurately reflect they were added - but if the user was already in the Crowd group, but listed on a different page, nothing will be written to the Crowd audit log.
.
Seems to me the resolution is straightforward -
Eliminate pagination for delegated administrators in the display of Crowd group members, and display ALL group members in a single page.
I just spent a fair amount of time tracking down this issue in our Crowd instance.
.
In my experience this problem is a function of being a Crowd "platform administrator" versus being a "delegated administrator" for a particular Crowd group. At least in Crowd 5.1.0, the users in a Crowd group are NOT subject to pagination for a platform administrator. But for someone who is not a platform admin, and only has access to manage specific groups, pages are used to display the group members. If the non-admin attempts to add someone NOT on the current page, the GUI will appear to "add" the user. If the user wasn't already in the group, the Crowd audit log will accurately reflect they were added - but if the user was already in the Crowd group, but listed on a different page, nothing will be written to the Crowd audit log.
.
Seems to me the resolution is straightforward -
Eliminate pagination for delegated administrators in the display of Crowd group members, and display ALL group members in a single page.