I'm integrating OpenLDAP as an LDAP Directory component in the open source Collabograte project that I recently announced:
http://kartiksubbarao.com/announcing-collabograte
Here are some areas of integration configured with OpenLDAP: + Username and password authentication to MediaWiki, WordPress Multisite, Cyrus IMAP, Sympa, and ejabberd + LDAP Groups used as Sympa Mailing Lists and ejabberd groups
If you want to see the implementation details, you can look at the puppet manifest and other files:
https://github.com/kartiksubbarao/collabograte/blob/master/puppet/modules/op...
https://github.com/kartiksubbarao/collabograte/tree/master/puppet/modules/op...
https://github.com/kartiksubbarao/collabograte/tree/master/puppet/modules/op...
I'd be very interested in hearing any comments, ideas, suggestions, or questions you might have on this. I want to help Enterprise IT do a better job of integrating open source into their environments, as well as improve the collaboration between Enterprise IT and open source project communities.
Please feel free to respond here, on the Collabograte mailing list, or email me directly, whichever you prefer.
Thanks,
-Kartik
On 01/03/12 22:17, Kartik Subbarao wrote:
I'm integrating OpenLDAP as an LDAP Directory component in the open source Collabograte project that I recently announced:
I think this is interesting and very worthwhile. There are similar projects like FusionForge, some of them use OpenLDAP. Can you elaborate on what makes Collabograte distinctive from those other alternatives?
I'd be very interested in hearing any comments, ideas, suggestions, or questions you might have on this. I want to help Enterprise IT do a better job of integrating open source into their environments, as well as improve the collaboration between Enterprise IT and open source project communities.
Other popular collaboration apps that come to mind are MoinMoin, Bugzilla, mailman
Do you plan to offer choice of app, e.g. someone can choose between Bugzilla, Mantis or RT for bug/service request handling?
Or you anticipate a very tight integration with the apps you prefer?
On 03/03/2012 08:11 AM, Daniel Pocock wrote:
On 01/03/12 22:17, Kartik Subbarao wrote:
I'm integrating OpenLDAP as an LDAP Directory component in the open source Collabograte project that I recently announced:
I think this is interesting and very worthwhile. There are similar projects like FusionForge, some of them use OpenLDAP. Can you elaborate on what makes Collabograte distinctive from those other alternatives?
The primary audience for Collabograte is IT integrators who want to assemble their own custom services from individual collaboration components that they choose. Collabograte helps them with the heavy lifting of integration -- connecting the dots between these different components. For example, in the role of "LDAP Directory Component", Collabograte can provide configurations for a number of LDAP servers. OpenLDAP is the first one that it supports, but there is no restriction on the products that can be supported. The same is true for any other category of component. So down the line, Collabograte might support 5 different OSes, 4 different LDAP servers, 3 different Wikis, etc.
Over time, someone could build a FusionForge out of Collabograte and make it generally available on the Internet (it's all open source, people can do whatever they want), but that's not the focal point of Collabograte itself. With Collabograte, I'm more interested in building a community of IT integrators than in providing services directly to end users. To put it in LDAP terms, Collabograte is more of an auxiliary class than a structural class :-)
I'd be very interested in hearing any comments, ideas, suggestions, or questions you might have on this. I want to help Enterprise IT do a better job of integrating open source into their environments, as well as improve the collaboration between Enterprise IT and open source project communities.
Other popular collaboration apps that come to mind are MoinMoin, Bugzilla, mailman
Thanks for the application suggestions.
Do you plan to offer choice of app, e.g. someone can choose between Bugzilla, Mantis or RT for bug/service request handling?
Or you anticipate a very tight integration with the apps you prefer?
The former, most definitely. Collabograte is all about freedom and choice, maximizing the options that integrators have to pick and choose the components they want. Basically, if someone is willing to contribute integration configuration for a new component, and the code meets a basic standard of quality, I'll lean towards accepting it. This may mean that not all combinations of all components will work with each other, but the ones people care about the most will. And I will be looking to build on existing work to make it more modular, get stuff pushed upstream where appropriate/possible, etc.
-Kartik
On 03/03/12 19:42, Kartik Subbarao wrote:
On 03/03/2012 08:11 AM, Daniel Pocock wrote:
On 01/03/12 22:17, Kartik Subbarao wrote:
I'm integrating OpenLDAP as an LDAP Directory component in the open source Collabograte project that I recently announced:
I think this is interesting and very worthwhile. There are similar projects like FusionForge, some of them use OpenLDAP. Can you elaborate on what makes Collabograte distinctive from those other alternatives?
The primary audience for Collabograte is IT integrators who want to assemble their own custom services from individual collaboration components that they choose. Collabograte helps them with the heavy lifting of integration -- connecting the dots between these different components. For example, in the role of "LDAP Directory Component", Collabograte can provide configurations for a number of LDAP servers. OpenLDAP is the first one that it supports, but there is no restriction on the products that can be supported. The same is true for any other category of component. So down the line, Collabograte might support 5 different OSes, 4 different LDAP servers, 3 different Wikis, etc.
It is interesting that you are posting about this on the OpenLDAP list, I also came here just recently with similar aims in mind:
https://sourceforge.net/mailarchive/message.php?msg_id=28879194
One of the challenges I've come across is deciding how to reconcile the user ID naming conventions, e.g.
- Moin (and some other wikis) have a convention of WikiNames, e.g. DanielPocock, so that you can have a `user' page such as http://wiki.example.org/DanielPocock
- some apps (e.g. bugzilla, git/gitosis, mailman, sympa) are using email address
- for some apps (e.g. Drupal) it is common to use OpenID, but also have an `alias' on the site itself, such as daniel.pocock, dpocock (or my favourite, sneaky_troll)
- and some apps (like granting UNIX access) require a short and concise user ID like dpocock
I'd be interested in any comments you have on that subject: you anticipate asking users to use all of these IDs? Or just go for the lowest common denominator (e.g. an ID like dpocock) and an email address?
I will have a look over the architecture of your solution. I had imagined implementing some kind of workflow system (maybe using Apache Camel, for example) that would take input events such as `new user' or `password change' and would then asynchronously propagate the event to all the components.
My objective in doing this, however, is actually to support another project, http://www.lumicall.org http://www.sip5060.net and http://www.opentelecoms.org - basically, I'm building a collection of sites to facilitate open, secure, federated SIP, and I'm looking at how to integrate the collaborative tools to support them, rather than just dumping it all on sourceforge or github.
On 03/03/2012 05:40 PM, Daniel Pocock wrote:
It is interesting that you are posting about this on the OpenLDAP list, I also came here just recently with similar aims in mind:
[...]
Daniel, can we take this discussion over to the Collabograte mailing list? The topic is drifting from OpenLDAP itself and I'm eager to get some discussions going on the Collabograte list:
http://groups.google.com/group/collabograte
Thanks,
-Kartik
openldap-technical@openldap.org
-
Daniel Pocock -
Kartik Subbarao