[consulting] consulting Digest, Vol 53, Issue 30

[Sami Khan]

Would recommend using LDAP. That way you won't have to tie anything into
Drupal.

Sami

On Fri, 2010-06-25 at 00:29 -0500, Sarah Poger Gladstone wrote:
> The level of integration I am looking for is just single-sign on so
> that anyone with a Drupal user name and password can seamlessly log
> into Moodle.   Then picking a similar color scheme for the Moodle
> theme so that it compliments the Drupal theme.
> 
> I am NOT planning to tie content from from one to the other, or any
> other connectivity.
> 
> Some links I have looked at for single sign on:
> http://drupal.org/project/moodle    and
> http://moodle.org/mod/data/view.php?d=13&rid=2941&filter=1
> 
> Thanks,
> Sarah
> 
> On Thu, Jun 24, 2010 at 1:16 PM, Sami Khan <sami at etopian.net> wrote:
> > On Thu, 2010-06-24 at 11:06 -0400, Joe Murray wrote:
> >
> >> Just to echo parts of what Sami and Tim are saying: try to keep the
> >> level of integration required between the Moodle and Drupal/CiviCRM
> >> parts of the site to a minimum. Where it is necessary, try to make it
> >> as thin and standardized as possible, or as loose and distant as
> >> possible. For example, give Moodle and Drupal/CiviCRM complementary
> >> but separate branding, so you don't have to replicate changes in both
> >> environments, especially not simultaneously. It might even be good to
> >> make one application a subdomain, eg crm.mycongregation.org. Also, you
> >> might want to try to avoid developing integrated login by using LDAP
> >> for single sign-on, though of course setting that up for Moodle and
> >> Drupal / CiviCRM can be its own small kettle of fish. The objective as
> >> I see it would be to avoid having to maintain middleware code that
> >> would have to be kept in synch with two or more projects that each has
> >> its own upgrade cycle.
> >
> > Agree. The problem is that there is no middle ware. Any such work often
> > ends up corrupting one of the systems with tons of hacks that are not
> > easily maintained. Also, it never looks like one app and expending
> > resources to make it look like one is a waste of time.
> >
> >>
> >> As this is starting to become fairly complex but is really useful for
> >> your vertical, you might want to make it into a SaaS offering so that
> >> the setup and maintenance costs (and expertise) can be reduced through
> >> scale and allocated to more customers.
> >
> > Agree.
> >
> > _______________________________________________
> > consulting mailing list
> > consulting at drupal.org
> > http://lists.drupal.org/mailman/listinfo/consulting
> >
> 
> 
>