You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The API to run GetClientxxx methods is unnecessarily clunky.
I realize this is not necessarily a bug, but i'm having trouble understanding logic behind the current implementation, which makes for an overly verbose operation, when considering that the "clientid" parameter is unique in KeyCloak.
To Reproduce
Try to get a client's secret with the Client ID:
Expected behavior
This should return the client secret of the client with the client ID of "my-client"
Additional context
Instead, we have to first define a string, run GetClients with the pointer of the string, and then run GetClientSecret with a dereferenced pointer of the first index of the response from GetClients
Describe the bug
The API to run GetClientxxx methods is unnecessarily clunky.
I realize this is not necessarily a bug, but i'm having trouble understanding logic behind the current implementation, which makes for an overly verbose operation, when considering that the "clientid" parameter is unique in KeyCloak.
To Reproduce
Try to get a client's secret with the Client ID:
Expected behavior
This should return the client secret of the client with the client ID of "my-client"
Additional context
Instead, we have to first define a string, run
GetClients
with the pointer of the string, and then runGetClientSecret
with a dereferenced pointer of the first index of the response fromGetClients
The text was updated successfully, but these errors were encountered: