I want to offer continued discussion on the JPA implementation in the
IDM project.
The work that Pedro did is restored here in the following workspace:
https://github.com/picketlink/picketlink-idm-restored
A testcase that is useful for JPA implementation in IDM is:
https://github.com/picketlink/picketlink-idm-restored/blob/master/impl/sr...
It is the exact mirror of the LDAP implementation:
https://github.com/picketlink/picketlink-idm-restored/blob/master/impl/sr...
These two implementations have very minimal user configuration.
The challenge is when users bring in complex database schemas and LDAP
DITs into operation. But the goal of balancing complexity with
usability is a tough one.
On 09/06/2012 10:13 AM, Anil Saldhana wrote:
Similar challenges exist for LDAP bindings also, since user LDAP
DITs
may be different. But we have to balance complexity with usability. :)
On 09/06/2012 07:37 AM, Pedro Igor Silva wrote:
> Ok. I'll take a look how he took care of that.
>
> Regards.
> Pedro Igor
>
> ----- Original Message -----
> From: "Anil Saldhana" <Anil.Saldhana(a)redhat.com>
> To: security-dev(a)lists.jboss.org
> Sent: Wednesday, September 5, 2012 6:52:35 PM
> Subject: [security-dev] PicketLink IDM JPA Identity Store
>
> Pedro,
> Shane just referred me to the following:
>
>
https://github.com/seam/security/blob/develop/impl/src/main/java/org/jbos...
>
> Can you adapt your work to incorporate all facets of this Seam work?
> Shane says users have varying db schema structures and the JPA
> implementation in seam3 took care of the nuances.
>
> Regards,
> Anil
>