[keycloak-user] kcadm update client seems to ignore defaultClientScopes

[Marek Posolda]

There are separate REST API operations for add/remove default client 
scope or optional client scope. I suggest to try admin console with 
browser and inspect the REST request, which admin console is doing for 
add/remove client scopes for client. This may show you how the REST 
request looks like and you should be able to "translate" this into 
proper format for kcadm then.

Marek

On 17/01/2019 05:27, Matt Evans wrote:
> Has anyone noticed that updating a client using kcadm seems to ignore the
> defaultClientScopes property?
>
> /opt/keycloak/bin/kcadm.sh update
> clients/366b5cb2-f4ac-4b81-9ccb-1e8198fec9f9 -r therealm -s
> 'defaultClientScopes=["web-origins"]' -s name=changedName --no-config
> --server http://localhost:8080/auth --realm master --user admin --client
> admin-cli --password xxxx
>
> We can update other properties ok, e.g. name, client id, redirectUris all
> update ok, but defaultClientScopes doesn't change. Also I think
> optionalClientScopes doesn't change either.
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user