Repository navigation
Conversation
|
cc @ahus1 I'm totally ok if maintainers edit this PR. Merging this PR helps a lot to others who need to work with Account API e.g. create custom Account Console |
There was a problem hiding this comment.
Thanks for your PR! Changes look good to me, just a few nitpicks :)
There was a problem hiding this comment.
This would be great to get in, but it needs a bit of work.
We should not have a single docs for both account and admin I'd say, but rather have two separate docs.
The annotations here also need some more review and tuning.
For example this is not the right URL (it should be /realms/{realm}/account)
Another example is CORS preflight stuff shouldn't be listed I'd say:
If you're still wanting to work on this, I'd be happy to review it in more depth and can also work on the website side of things if you want.
|
@thomasdarimont I'm ok if maintainers will do all changes that they think we need to do. @stianst I wrote reasons in description about why it's done like this. I consider this ok solutions, since right now keycloak don't have any documentation for Maintainers, please adjust whatever you think to need to adjust. Let's not put this changes in forgotten mode. |
Signed-off-by: Yevhen Tienkaiev <hronom@gmail.com>
47fc76c to
e2237f1
Compare
Signed-off-by: Yevhen Tienkaiev <hronom@gmail.com>
|
@Hronom I'm afraid at this point we don't have capacity to work on this PR, and as I mentioned it really should be a separate set of docs, as the use-case is completely different, it's a completely different API, and the admin API is already way to big and confusing on its own not to intermix it with account API. It should not be particularly hard to adjust your PR to do that, and as I mentioned before if you did that I'd be happy to help with doing the updates needed to get it publishes. |
|
@stianst you probably really out of context and didn't read description of the PR. And I would say this is the reasons why Accounts API still don't have documentation, because whenever maintainers of Keycloack tried to do it the hit same wall as I and drop work on it. There was done CRITICAL architecture mistake in the beginning when Accounts API was created. |
Extend OpenAPI documentation with Account API.
This should help with this #13203 but there some nuances.
How-to check
Generate schema:
Check generated file in:
Nuances
There issue related to how API organized.
Specifically there sub resources here:
and here:
During generation of OpenAPI plugin
smallrye-open-api-maven-pluginnot able to to get a clue about what Sub Resource will be returned by was methods.So in order to provide at least something instead of nothing(for Account API) - there was added groups of fake methods in
AccountLoader.This allow*-example paths.
smallrye-open-api-maven-pluginto generate OpenAPI spec. However it generates them underTo make it actual we need to do simple replace of
/account-api-cors-exampleand/account-api-exampleto empty string. This helps developers to easily adopt generated OpenAPI for other services that need to use Account API.