+1 There's a lotWe could also use the extra level of tabs we have used on security defencesOn 19 October 2015 at 14:55, Bill Burke <bburke@redhat.com> wrote:I think we have too many tabs on client page. Maybe if the roles tab is moved off?
On 10/19/2015 2:32 AM, Stian Thorgersen wrote:
Instead of having the create and edit pages different. Why don't we have
only those fields shown by default, then have a expandable field or a
separate tab with the "advanced options"?
On 16 October 2015 at 20:24, Bill Burke <bburke@redhat.comkeycloak-dev@lists.jboss.org <mailto:keycloak-dev@lists.jboss.org><mailto:bburke@redhat.com>> wrote:
I'd like to improve the client creation page to reduce the amount of
info somebody needs to type in the first page and to provide base
defaults. I'll add this as a jira and schedule for 1.7 or 1.8
Create page required config (only these will be shown):
* Client Id
* protocol
* Root URL
For OIDC defaults would be:
* confidential client
* full scoped
* valid redirect urls Root URL/*
* consent required false
* direct grants only false
* service accounts enabled false
* Base URL renamed to Link URL defaults to root url
* Web Origins defaults to host of Root URL
* Remove admin url, this would just point to the root.
For SAML:
* Sign documents true
* Include Authn Statement true
* Client signature required true
* Sign assertions false
* Client private/public cert would be generated
* force post binding false
* encrypt assertions false
* front channel logout false
* Remove valid redirect URLs
* Remvoe Master SAML Processing URL
* Assertion Consumer and Logout Service binding urls all filled in with
Root URL.
SAML would get an Installation tab and could choose configurations for:
* Keycloak SAML adapter
* mod-auth-mellon
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
https://lists.jboss.org/mailman/listinfo/keycloak-dev