fix: remove explicit pagination from Logto role API calls
Logto's /api/roles/{id}/users endpoint rejects page=1 with
guard.invalid_pagination. Remove explicit pagination params and
let Logto use its defaults.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -704,7 +704,7 @@ public class LogtoManagementClient {
|
||||
public List<Map<String, Object>> listRoleUsers(String roleId) {
|
||||
var token = getAccessToken();
|
||||
var response = restClient.get()
|
||||
.uri(config.getLogtoEndpoint() + "/api/roles/" + roleId + "/users?page=1&page_size=200")
|
||||
.uri(config.getLogtoEndpoint() + "/api/roles/" + roleId + "/users")
|
||||
.header("Authorization", "Bearer " + token)
|
||||
.retrieve()
|
||||
.body(List.class);
|
||||
@@ -718,7 +718,7 @@ public class LogtoManagementClient {
|
||||
var response = restClient.get()
|
||||
.uri(config.getLogtoEndpoint() + "/api/roles?search=" +
|
||||
java.net.URLEncoder.encode(roleName, java.nio.charset.StandardCharsets.UTF_8) +
|
||||
"&page=1&page_size=20")
|
||||
"&page_size=20")
|
||||
.header("Authorization", "Bearer " + token)
|
||||
.retrieve()
|
||||
.body(List.class);
|
||||
|
||||
Reference in New Issue
Block a user