<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 17 December 2015 at 14:39, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I don't think you've thought this through. Of course you would want scope on a client template.<br>
<br>
Client Template allows scope for Service A, Service B, and Service C.<br>
<br>
Client 1, Client 2, and Client 3 all need to access Service A, B, and C. You'd have to define scope in each client when it would be easier to define it in the client template.</blockquote><div><br></div><div>I have thought it through - I just think that it's a lot more likely that Client 1 will invoke Service A, Client 2 will invoke Service B. Even if all clients invoke all services they will not have the same scope, but different scope.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 12/17/2015 3:58 AM, Stian Thorgersen wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Not sure we even need scope in client templates? Isn't it sufficient to<br>
only have scope control on a per-client?<br>
<br>
For example say there's 3 clients in a group of clients:<br>
* service - user and admin roles<br>
* user console<br>
* admin console<br>
<br>
You don't want the user console to have scope on the admin console just<br>
because it's in the same group. Also, you don't want the service to have<br>
any scope.<br>
<br>
Can anyone come up with an example where scope on the client template<br>
would be useful?<br>
<br>
On 16 December 2015 at 14:22, Marek Posolda <<a href="mailto:mposolda@redhat.com" target="_blank">mposolda@redhat.com</a><br></span><span class="">
<mailto:<a href="mailto:mposolda@redhat.com" target="_blank">mposolda@redhat.com</a>>> wrote:<br>
<br>
On 15/12/15 18:34, Bill Burke wrote:<br>
> So, what to do about scope and client templates? Client templates could<br>
> have "full scope allowed" or define a scope. A client would either<br>
> click "full scope allowed" or it can add additional scoped roles.<br>
><br>
> Sound ok?<br>
><br>
yes to me. I suppose each client will still automatically receives his<br>
own client roles to the scope like it's now.<br>
<br>
Marek<br>
_______________________________________________<br>
keycloak-dev mailing list<br></span>
<a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a> <mailto:<a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a>><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
<br>
<br>
</blockquote><div class="HOEnZb"><div class="h5">
<br>
-- <br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" rel="noreferrer" target="_blank">http://bill.burkecentral.com</a><br>
</div></div></blockquote></div><br></div></div>