[keycloak-dev] implement JPA model

[Anil Saldhana]

Bill,
   this is just a cop out.

You very well know this is just going to create more headache
if ever KeyCloak is integrated into Wildfly. :)

In future versions of WF (starting WF9), we want to make use of PL IDM
for the user stores across the subsystems. That is the reason we are
implementing a JDBC store implementation in addition to the JPA store when
a database is involved.

Unfortunately KeyCloak implementing its own JPA model will just increase
the technical debt when we deal with an integrated system such as WildFly
from a developer user experience perspective. :(

Regards,
Anil

On 11/01/2013 10:02 AM, Bill Burke wrote:
> Keycloak is designed right now so that we can easily swap out
> persistence engines.
>
> I can't wait for PL 2.5.3 to be released so I can use it with Wildfly.
> I'll have a JPA model done by today so I can start bundling and testing
> Keycloak with Wildfly tomorrow.  We'll revisit Picketlink again in the
> next Keycloak release to see if it makes sense to take advantage of its
> LdAP/AD integration.  Right now though, I think we can get the biggest
> performance improvements from maintaining our own persistence engine and
> by putting targeted caching in front of it.
>
>
> On 11/1/2013 10:22 AM, Anil Saldhana wrote:
>> And I fall off the chair.
>>
>> On 11/01/2013 09:22 AM, Bill Burke wrote:
>>> FYI, I'm currently implementing a JPA model.  Will switch to that
>>> instead of Picketlink when its done.
>>