Hi Marek I took your advice and looked at what the console does. It seems that you have to individually PUT or DELETE each client scope in the defaultClientScopes and optionalClientScopes. e.g. PUT /clients/<client id>/defaultClientScopes/<scope id> I tried to PUT to the /clients/<client id>/defaultClientScopes endpoint to set all the default client scopes in one go but the method is not allowed. We currently have our clients deployed using ansible calling kcadm with the json template, this works well for creating new clients, the default client scopes are set correctly, but the update of an existing client template ignores them if they are specified in the json. Whilst we can add more code to extract the scopes from the template and individually call DELETE or PUT to adjust them it seems overly complicated. I guess for now we will delete and create the whole client if we need to update them. Are there plans to improve this in the future? It seems inconsistent that the rest endpoint for the client just ignores those properties for updates, but accepts them for creates. Thanks Matt On Thu, 17 Jan 2019 at 22:20, Marek Posolda <mposolda(a)redhat.com&gt; wrote: