ClientScope - Keycloak API Docu vs. Admin-client vs. Admin-ui #16086

AmusedShadow · 2022-12-19T22:06:55Z

AmusedShadow
Dec 19, 2022

In case of creating with the admin ui a new client scope, it get's an type.

{
    "name": "test",
    "description": "",
    "attributes": {
        "consent.screen.text": "",
        "display.on.consent.screen": "true",
        "include.in.token.scope": "true",
        "gui.order": ""
    },
    "type": "optional",
    "protocol": "openid-connect"
}

But this property type is neither part of the ClientScopeRepresentation within the admin-client package nor it is part of the official REST API Docu ClientScopeRepresentation ...
https://www.keycloak.org/docs-api/14.0/rest-api/#_clientscoperepresentation

Is it now a bug, a hidden feature or just some whit noise ?

edewit · 2022-12-20T14:40:01Z

edewit
Dec 20, 2022
Collaborator

in the UI it's shown as a property of scope, but it's not. There are separate endpoints to control the type: namely /default-default-client-scopes and /default-optional-client-scopes

0 replies

AmusedShadow · 2022-12-20T15:48:01Z

AmusedShadow
Dec 20, 2022
Author

Ah ok. Because the ui sends within the create request. That was a little confusing :)

0 replies

Navigation Menu

Repository navigation

ClientScope - Keycloak API Docu vs. Admin-client vs. Admin-ui #16086

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

ClientScope - Keycloak API Docu vs. Admin-client vs. Admin-ui #16086

Uh oh!

AmusedShadow Dec 19, 2022

Replies: 2 comments

Uh oh!

Uh oh!

edewit Dec 20, 2022 Collaborator

Uh oh!

AmusedShadow Dec 20, 2022 Author

AmusedShadow
Dec 19, 2022

edewit
Dec 20, 2022
Collaborator

AmusedShadow
Dec 20, 2022
Author