With FusionAuth 1.17.4 and accessing the API through the Java client API (latest version 1.17.0) I was surprised today when removing group memberships via:
fusionAuthClient.deleteGroupMembers(MemberDeleteRequest(groupIds: List<UUID>))
that the request gets executed successfully and the user is disassociated from the form group memberships, but unfortunately the application roles seem to stick with the user: as if the group inherited roles have been moved down into the application registration.
When I remove a membership with the help of the FusionAuth Web UI the expected behaviour is fine and the user gets also the roles which indirectly via the group membership disassociated.
Could you please clarify why the API behaves differently vs. is it expected to update the application roles on the user additionally?