Hi Kambiz, appreciate that this thread has fallen by the wayside. I've created a ticket on the security addon so at least it doesn't get forgotten; please comment there. Thx Dan
https://github.com/isisaddons/isis-module-security/issues/37 On 16 May 2016 at 07:30, Dan Haywood <[email protected]> wrote: > Hi Kambiz, > > Sorry not to reply sooner, have been finishing off work on the new > InteractionContext stuff (see email just posted to users@ mailing list). > > As to your request, have no problem in helping break out the security > module to allow different persistence implementations. My thinking is that > I'll factor out some interfaces etc (as Oscar was suggesting) then you guys > can plug in your own impl. > > To do this properly will probably require that the current single "dom" > artifact will need to break into several different submodules. That might > require some minor updates to pom.xml and AppManifests, but nothing too > onerous, I think. > > Let me look at it in more detail over the next couple of days. > > Thx > Dan > > > 2016-05-13 16:01 GMT+01:00 Óscar Bou - GOVERTIS <[email protected]>: > >> Hi Kamiz, >> >> The interface (or abstract class) would be on the Isis Security add-on >> and your custom implementation on your own Domain jar (despite we could >> also provide it as an anternative implementation on the security add-on >> afterwards). >> >> >> >> >> El 13 may 2016, a las 16:10, Kambiz Darabi <[email protected]> >> escribió: >> >> Hi Óscar, >> >> On 2016-05-12 17:17 CEST, Óscar Bou - GOVERTIS <[email protected]> >> wrote: >> >> 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 ... >> >> >> Do they have to be separated into different dependencies (= jars)? >> Or what is the correct way of avoiding the automatic mapping of the >> JDO annotated classes to the current default data store? >> >> Could this approach help? >> >> >> Definitely. >> >> The Shiro realm would use LDAP attributes to handle >> authentication/authorization. >> >> >> Yes, LDAP users and group membership information. >> >> Cheers >> >> >> Kambiz >> >> >> >> Óscar Bou Bou >> Socio - IT & GRC Management Services Director >> m: +34 620 267 520 >> s: <http://www.govertis.com>www.govertis.com e: [email protected] >> >> LinkedIn: 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. >> >> >
