Hi Peter,

Thanks for evaluating Centric CRM, and I'm glad you like it.

We have one community member who has done an LDAP integration, but has not yet contributed their code. Last I heard, they were using it internally (are you listening, Adam?).

I would think the LDAP integration would not be such a big job. The ACL piece seems both very interesting and more substantial. We've had others interested in something similar in the past.

On both counts we would be happy to have you as a development partner and would provide whatever assistance we could to make your job easy and successful as possibe, including help with internal architecture and such. In order to make your code maintainable by our core team so we can carry it forward to new versions, we would ask only that you follow some common sense development rules and work closely with our core development team.

If you are really interested in taking some of this on, I could contact you offline, and we could discuss how to proceed. We'd probably end up building a public project to document the work and solicit community advice and support.

We're pretty flexible, just let me know how you'd like to proceed.

Thanks again for your interest and support!

Tom

Community,

we've got LDAP authentication working with Centric CRM 3.0 test 2.

- user details are stored in Centric's DB as before
- LDAP is authorative password source; password change in Centric CRM has no effect, and doesn't write to LDAP

Mapping to LDAP object:
--- username(Centric) === email(LDAP)

When user logs in:
- login module connects to LDAP read-only
- their username===email is searched for in LDAP
- if they are found in LDAP exactly once, their DN and password they entered is used to authenticate against LDAP
- if everything was OK, user is let in to Centric CRM

TODO:
- how to store LDAP settings in Centric CRM config files, and GUI to configure them
- how to map user between DB <-> LDAP - options/tips above
- how to configure DB <-> LDAP user mapping

Just to clarify - would it not be interesting to have a common address book functionality? centric could either be an LDAP server (should not be so hard) so that I can connect with my clients to view the data there; or all user/address info should be externalized on an LDAP server, so address maintenance is done outside of centric. Best of all would be two way, of course :-)

The goal would be to maintain addresses only once, and do so from your standard client (well, which one can write to LDAP, but oh well, one can dream), and all apps have access to that info.

What you do is more like a single sign on solution, it seems. Do you plan to extend into above directions?

Cheers
Boris Kraft