IMO that's a mistake, there's a lot of duplicated code, and you'll also want
to support social login etc. (so more duplicated code) or SaaS when/if it comes to a free
"trial" online.
As admin is a JavaScript application it is clearly a remote application and could login
the same way as any other remote application does, i.e. through TokenService. The only
difference in the two scenarios is that for the admin rest endpoints it would be a small
optimization to allow validating the token without a remote call, which would be
beneficial for folks that wants to use keycloak for smaller internal deployments (e.g. a
single app server running a rest/js style app).
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Monday, 5 August, 2013 7:26:06 PM
Subject: Re: [keycloak-dev] SaaS login
TokenService is really for a remote service that is using keycloak to
authenticate. Its all the same server so no need for the extra
redirects and thus no need for the Token Service endpoints.
On 8/5/2013 11:14 AM, Stian Thorgersen wrote:
> I was wondering why there are separate login/logout endpoints in
> SaasService? Should this not use the standard mechanism to do this (i.e.
> TokenService)?
> _______________________________________________
> 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