isis-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Óscar Bou - GOVERTIS <o....@govertis.com>
Subject Re: Isis security module questions
Date Thu, 12 May 2016 15:17:16 GMT
Hi, Kambiz.

Interesting.

Regarding Users and Roles current implementation, perhaps we could refactor it using interfaces,
giving:
- a default implementation (the current JDO-based one that persists to the database).
- a new one based on the DN LDAP repository support, extending that interface, that you could
implement [1].

Could this approach help?

@Dan 
perhaps some alternative/complementary approach based on mixins contributing also to domain
entities “marked” with those Interfaces?


The Shiro realm would use LDAP attributes to handle authentication/authorization.


HTH,

Oscar


[1] http://www.datanucleus.org/products/datanucleus/datastores/ldap.html





> El 12 may 2016, a las 13:31, Kambiz Darabi <darabi@m-creations.com> escribió:
> 
> Hi,
> 
> we are trying to use the security module which would be a perfect fit
> for our needs if it had a fully LDAP based implementation.
> 
> To make things even more difficult, we are building up an infrastructure
> where several domains with separate databases exist.
> 
> Problem 1: the JDO annotations of the domain objects in the module
> obviously don't use the DataNucleus extension to specify a different
> data store than the default one.
> 
> This leads to users/roles being created in the 'default data store' of
> the respective service and we are not easily able to redirect the
> security related persistence towards a central 'security database'.
> 
> Problem 2: a fully LDAP based implementation is what the customer needs
> 
> If an LDAP backend is present in a company, then one would expect to
> handle all of the authentication/authorisation issues on that side
> without the need to have an additional database which might get out of
> sync with the single source of truth which should be LDAP.
> 
> We have found out that DataNucleus even has an LDAP data store
> implementation.
> 
> Would it be possible to implement a fully LDAP based backend for the
> security module? We would be willing to invest some effort, if you could
> guide us on how to tackle the problem.
> 
> Thanks
> 
> 
> Kambiz
> 
> 
> Kambiz Darabi
> -- 
> m-creations gmbh
> Acker 2
> 55116 Mainz
> Germany
> 
> W: http://www.m-creations.com
> E: darabi@m-creations.com
> T: +49 6131 6224417
> F: +49 6131 6224418
> --
> Registered Office: Mainz, HRB Mainz 7382
> Managing Directors: Frank Pacholak, Kambiz Darabi



Óscar Bou Bou
Socio - IT & GRC Management Services Director
m: +34 620 267 520
s:  <http://www.govertis.com/>www.govertis.com <http://www.govertis.com/> e: o.bou@govertis.com
<mailto:o.bou@govertis.com>

LinkedIn: https://www.linkedin.com/in/oscarbou <https://www.linkedin.com/in/oscarbou>
Twitter: 	@oscarbou <https://twitter.com/oscarbou>



Este mensaje y los ficheros anexos son confidenciales. Los mismos contienen información reservada
que no puede ser difundida. Si usted ha recibido este correo por error, tenga la amabilidad
de eliminarlo de su sistema y avisar al remitente mediante reenvío a su dirección electrónica;
no deberá copiar el mensaje ni divulgar su contenido a ninguna persona.

Su dirección de correo electrónico junto a sus datos personales constan en un fichero titularidad
de GOVERTIS ADVISORY SERVICES, S.L. cuya finalidad es la de mantener el contacto con Ud. Si
quiere saber de qué información disponemos de Ud., modificarla, y en su caso, cancelarla,
puede hacerlo enviando un escrito al efecto, acompañado de una fotocopia de su D.N.I. a la
siguiente dirección: GOVERTIS ADVISORY SERVICES, S.L. Avda Cortes Valencianas, 58 – 8º
- 6ª. 46015 - Valencia,  y Paseo de la Castellana, 153, 28045 - MADRID. Asimismo, es su responsabilidad
comprobar que este mensaje o sus archivos adjuntos no contengan virus informáticos, y en
caso que los tuvieran eliminarlos.



Mime
View raw message