Join the discussion: Admin API v2

[Václav Muzikář]

The Admin API is at the very heart of Keycloak as it makes Realm configuration possible in a unified way. Regardless what interface you use – let it be UI, CLI, Terraform Provider, Operator, or something else – it always calls the Admin REST API.

The current API however has some drawbacks, some of them as serious as blocker e.g. for harnessing the full Operator potential with it. As a first step towards the next-gen Admin API in Keycloak, we're currently working on some guidelines/blueprint that will cover how the API should be designed. The discussions around the design will be split into separate problems (e.g. HTTP verbs, versioning etc.), all grouped by a category on GitHub.

There are currently two new discussions (with more on the way):

• What is not working well with the current Admin APIs?
• API Resource Modeling Principles

I'd like to invite you to join the discussions as they will be coming in the upcoming weeks. The new API will be a big step in Keycloak's usability and we need your help to get it right!

Thanks.

--

Václav Muzikář

Principal Software Engineer, Keycloak

Red Hat

[Sebastian Łaskawiec]

Thanks Vasek for posting this!

On top of the existing discussion, I've just created another Discussion ticket about the Default Values. You can find it here [1].

Comments and feedback is more than welcome!

[1] https://github.com/keycloak/keycloak/discussions/38551

--
You received this message because you are subscribed to the Google Groups "Keycloak Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to keycloak-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/keycloak-dev/CAMQSZyjeRggRP7m-P6o%2BaCAAMdgtYnXiLwbvmoS4xMFhQnUsmw%40mail.gmail.com.