Inconsistencies in Admin API based user listing #10892
Labels
Feature: Account & User Info
Feature: API
Size: 10
A percentage of a sprint. 7 hours.
Type: Bug
a defect
User Role: API User
Makes use of APIs
User Role: Superuser
Has access to the superuser dashboard and cares about how the system is configured
What steps does it take to reproduce the issue?
Look at the outputs of
/api/admin/authenticatedUsers
and/api/admin/list-users
When does this issue occur?
When using the API to retrieve all users
Which page(s) does it occurs on?
API
What happens?
/list-users
endpoint is inconsistent with it's naming. Why isn't this paginated, searchable output enabled under/authenticatedUsers
?/list-users
endpoint doesn't use theJsonPrinter.json(AuthenticatedUser)
to include thepersistentUserId
in the JSON output, while the/authenticatedUsers
endpoints do. Instead, it uses theAuthenticatedUser.toJson()
converter, which is solely used for this purpose, nowhere else except a test of theAuthenticatedUser
class./authenticatedUsers
endpoint deprecated, when there are a lot more endpoints using this path?/api/users
instead of/api/admin/authenticatedUsers
when it does require a superuser token anyway?/api/admin/authenticatedUsers/{id}/{attribute}
?To whom does it occur (all users, curators, superusers)?
Superusers, Admins
What did you expect to happen?
See list above.
Which version of Dataverse are you using?
4.20 and
develop
.Any related open or closed issues to this bug report?
None that I could find.
The text was updated successfully, but these errors were encountered: