[keycloak-dev] implement JPA model

[Bill Burke]

Less moving parts is better than more moving parts, IMO.  There's also 
still the issue of IDs as names are not unique in our data model.  For 
performance also doesn't matter if this information is in a file or not 
as it can be cached in memory.

On 11/1/2013 11:39 AM, Stian Thorgersen wrote:
> Any chance of saving config in a single json file (maybe one per-realm), instead of in the database. That would be more than sufficient as long as the server is single-tenant and there's only a handful applications.
>
> For config I mean things like:
>
> Realm:
>
> * Name
> * Email settings
> * Require email validatation
> * Social settings
> * List of applications
> * ...
>
> Application:
>
> * Name
> * Management URI, redirect URIs
> * ...
>
> That would make it a lot simpler for devs to manage the server more like a traditional server if they want to.
>
> ----- Original Message -----
>> From: "Bill Burke" <bburke at redhat.com>
>> To: keycloak-dev at lists.jboss.org
>> Sent: Friday, 1 November, 2013 2:22:25 PM
>> Subject: [keycloak-dev] implement JPA model
>>
>> FYI, I'm currently implementing a JPA model.  Will switch to that
>> instead of Picketlink when its done.
>> --
>> Bill Burke
>> JBoss, a division of Red Hat
>> http://bill.burkecentral.com
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com