I've already mentioned this as part of the discussion around M1, but I thought it would make sense to create a separate thread for it here. I propose that we move the SaaS admin console into a separate project in github (http://github.com/keycloak/keycloak-admin?). This would allow releasing the console separately from the core Keycloak server. Also, it allows not deploying the SaaS admin console if it's not required (for example for MBaaS, or for a simple internal server where config files/cli is used instead). Also, I believe that the admin console should use TokenService for authentication, and that we drop all authentication, registration, etc. from SaasService. _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

Makes sense - I assume it would be a war module that can be deployed separately to the auth-server war? ----- Original Message ----- > From: "Bill Burke" <bburke(a)redhat.com&gt; > To: keycloak-dev(a)lists.jboss.org > Sent: Friday, 20 September, 2013 1:03:53 PM > Subject: Re: [keycloak-dev] Moving admin console into a separate project > > +1 on separate module, -1 on separate project. We can't really have a > separate project until we have an actual release of Keycloak. Open > source projects need to be able to build and run out the box. I'm not > having the admin UI work against snapshots. > > On 9/20/2013 7:39 AM, Stian Thorgersen wrote: >> I've already mentioned this as part of the discussion around M1, but I >> thought it would make sense to create a separate thread for it here. >> >> I propose that we move the SaaS admin console into a separate project in >> github (http://github.com/keycloak/keycloak-admin?). This would allow >> releasing the console separately from the core Keycloak server. Also, it >> allows not deploying the SaaS admin console if it's not required (for >> example for MBaaS, or for a simple internal server where config files/cli >> is used instead). >> >> Also, I believe that the admin console should use TokenService for >> authentication, and that we drop all authentication, registration, etc. >> from SaasService. >> _______________________________________________ >> keycloak-dev mailing list >> keycloak-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/keycloak-dev >> > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev >