I like the idea of an option to bind the auth server to the root
context. I think that would be especially good for the appliance dist.
But I'm not sure about the rest. What is the problem we are solving?
On 1/23/2015 6:23 AM, Stian Thorgersen wrote:
Our URLs are quite long, examples:
*
http://localhost:8080/auth/realms/master/protocols/openid-connect/login
*
http://localhost:8080/auth/realms/master/account
We could remove the 'realms' part and 'protocols' parts couldn't we?
*
http://localhost:8080/auth/master/oidc/login
*
http://localhost:8080/auth/master/account
That would require moving everything under a realm and I guess we'd need to hard-wire
the protocols, but I think that should be fine.
We also need to make sure we can just the root context:
*
http://localhost:8080/master/oidc/login
*
http://localhost:8080/master/account
We can also introduce other mechanisms to select the realm. For example a server with
single realm can just omit it altogether:
*
http://localhost:8080/oidc/login
*
http://localhost:8080/account
And we could allow setting what domains uses what realms:
*
http://keycloak-master/oidc/login
*
http://keycloak-other/oidc/login
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev