<div dir="ltr">BTW maybe we should do this after the feature freeze and focus on getting the last features in first?</div><div class="gmail_extra"><br><div class="gmail_quote">On 19 October 2015 at 14:57, Stian Thorgersen <span dir="ltr"><<a href="mailto:sthorger@redhat.com" target="_blank">sthorger@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>+1 There's a lot</div><div><br></div>We could also use the extra level of tabs we have used on security defences</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 19 October 2015 at 14:55, 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 think we have too many tabs on client page. Maybe if the roles tab is moved off?<span><br>
<br>
<br>
<br>
<br>
On 10/19/2015 2:32 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>
Instead of having the create and edit pages different. Why don't we have<br>
only those fields shown by default, then have a expandable field or a<br>
separate tab with the "advanced options"?<br>
<br>
On 16 October 2015 at 20:24, Bill Burke <<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a><br></span><div><div>
<mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>>> wrote:<br>
<br>
I'd like to improve the client creation page to reduce the amount of<br>
info somebody needs to type in the first page and to provide base<br>
defaults. I'll add this as a jira and schedule for 1.7 or 1.8<br>
<br>
Create page required config (only these will be shown):<br>
* Client Id<br>
* protocol<br>
* Root URL<br>
<br>
For OIDC defaults would be:<br>
* confidential client<br>
* full scoped<br>
* valid redirect urls Root URL/*<br>
* consent required false<br>
* direct grants only false<br>
* service accounts enabled false<br>
* Base URL renamed to Link URL defaults to root url<br>
* Web Origins defaults to host of Root URL<br>
* Remove admin url, this would just point to the root.<br>
<br>
For SAML:<br>
* Sign documents true<br>
* Include Authn Statement true<br>
* Client signature required true<br>
* Sign assertions false<br>
* Client private/public cert would be generated<br>
* force post binding false<br>
* encrypt assertions false<br>
* front channel logout false<br>
* Remove valid redirect URLs<br>
* Remvoe Master SAML Processing URL<br>
* Assertion Consumer and Logout Service binding urls all filled in with<br>
Root URL.<br>
<br>
SAML would get an Installation tab and could choose configurations for:<br>
* Keycloak SAML adapter<br>
* mod-auth-mellon<br>
<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>
_______________________________________________<br>
keycloak-dev mailing list<br></div></div>
<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><div>
<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></div></blockquote></div><br></div>