Just out of curiosity why do you not just integrate with the LDAP module that already exists? Is there a custom connector that is preventing it? We have worked out all sorts of things like automated Single Sign On, excluding groups from signing in so you can have generic accounts not authenticate and a whole slew of other features. It also has really good Active Directory and OpenLDAP connection ability and documentation already written. I'm one of the maintainers for it and I think we could accomidate OA integration.

Comments

mpotter’s picture

Status: Active » Closed (works as designed)

Umm, did you look at the code? This module definitely uses the LDAP module already (see the *.make and *.info files). We wrote an API layer between Open Atrium 2 and the LDAP layer so people could plug-in different user identity systems. For example, you can integrate the Simple LDAP module if you wish. But for the main integration we used the LDAP module and, in fact, submitted several patches to LDAP already for handling some features like email-based authentication.

haydeniv’s picture

Status: Closed (works as designed) » Active

Clearly I did not look at the code yet. D.o could really use some improvements on it's repository viewer so it is easier to do code reviews. I guess the project page could use some more information describing what this module does then. Something like:

This is an API module that adds a layer between Open Atrium 2 and the LDAP layer so that people can plug-in different user identity systems. Currently it integrates with LDAP module but is capable of integrating with other modules such as Simple LDAP or your own custom LDAP authenticator.

Also do you have a roadmap for things you would like to accomplish to get this module to a release? I'm looking into deploying OA for my organization and we rely heavily on LDAP as we have over 3000 users and I think I could justify some work time towards this.

mpotter’s picture

I updated the project page. But I think you'll want to look at the og_ldap_api module that we wrote to go with this. The Open Atrium LDAP module is really just a set of fields being added to some OA2 content types. All of the API work and plugins for LDAP backends is in the og_ldap_api module, which includes a submodule called og_ldap_api_ldap that provides the plugin between og_ldap_api and the actual ldap module.

Yeah, some of the naming schemes get a bit weird. But the idea was to implement LDAP for Organic Groups in a more generic way that didn't necessarily tie it to a single implementation. (and the project name og_ldap was taken because of an old D6 module).

Don't really have any roadmap at this point. Support is pretty minimal. It was something we needed for a specific client build so we decided to try and write it in a way that would best benefit the community. If you want to get involved and get added to the maintainer list, list me know. Certainly would welcome the help.

mpotter’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.