keycloak
keycloak copied to clipboard
kilork
Keycloak REST API Client
Currently, all string params are `Option` (57 occurrences). What do you think of switching all with `Option`? `auth_client: Option,` instead of `auth_client: Option,`.
To continue the discussion [here](https://github.com/kilork/keycloak/pull/7) and [here](https://github.com/kilork/keycloak/pull/16)... AFAIK, the main `grant_type`s for this case are `password` and `client_credentials`. For `password`, based on [this](https://www.oauth.com/oauth2-servers/access-tokens/password-grant/) article, we need `username` and `password` mostly....
Better to follow the same pattern for both structs. One has `acquire` the other one has `create`. One the `get` sends a request always, in the other one uses the...
Add client to implement same functions using command line interface.
Currently token would be refetched for each request, which is far from optimal. https://github.com/kilork/keycloak/blob/master/src/rest/mod.rs#L32 Introduced in #30 FYI: @criminosis
`Option` does not look nice. I would prefer to have something similar to `AsRef`. Basically it means we should be more flexible with parameters. This must be also checked from...
We currently support [reqwest](https://github.com/seanmonstar/reqwest). It would be nice to have other possibilities as well, for example [surf](https://github.com/http-rs/surf)
APIs start with `/admin/realms/{realm}/clients/{client-uuid}/authz/*` are not generated. I think it's cause by the `openapi.json` doesn't have tags of these apis.
We at wire are using this crate to test our oidc flow with keycloak running in dev mode in a docker container. Thanks a lot! However, we're currently running into...
