Start IDM using DS as the repo. Embedded is fine.
Follow steps outlined in https://bugster.forgerock.org/jira/browse/OPENIDM-16654 .
The last step there returns two results, which is the problem called out by that issue. However, when you are using DS as a repo a further bug can be observed when the "members" query uses a _sortKeys argument, like so:
curl -u openidm-admin:openidm-admin "http://localhost:8080/openidm/managed/role/feasels/members?_queryFilter=true&_sortKeys=_id"
For some reason, in this case there is only one result (it appears to be the first record that was created, but I'm not sure if that's consistent).
Note that this same behavior does not occur when using JDBC.
Also note that the IDM Admin UI always uses _sortKeys (default of _id if no other specified). Finally, the Platform Admin UI does not have a default _sortKeys, and so in that case both records will be returned (until the user chooses to sort by a column, at which point only one relationship per distinct vertex will be returned).