Nothing to add about OpenID, but I second Sami's recommendation of the LDAP approach.<br clear="all"><br>Best regards,<br>Fureigh<br><br>---<br><a href="http://fureigh.com">fureigh.com</a><br>347.469.0925<br>
<br><br><div class="gmail_quote">On Sat, Jun 26, 2010 at 11:42 AM, Sarah Poger Gladstone <span dir="ltr"><<a href="mailto:listmember@gladstone.info">listmember@gladstone.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Sami - Thanks for the links on LDAP, that looks like a solid path to single sign on. <div><br></div><div>I have looked at OpenID previously, but I think it would be challenging for the low-tech community members to deal with. The main pain points I noticed is that if someone does not yet have an OpenID, getting one is a several step process. If the person has one, they do not know which url to provide, and the sign in process is multi-step. </div>
<div><br></div><div>Any ideas/pointers for a successful roll-out of a Drupal site using OpenID with a _very_ low-tech crowd? </div><div><br></div><font color="#888888"><div>-Sarah</div><div><br></div></font><div><div><div>
</div><div class="h5"> <br><br><div class="gmail_quote">On Fri, Jun 25, 2010 at 12:45 AM, Sami Khan <span dir="ltr"><<a href="mailto:sami@etopian.net" target="_blank">sami@etopian.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">LDAP:<br>
<br>
<a href="http://docs.moodle.org/en/LDAP_authentication" target="_blank">http://docs.moodle.org/en/LDAP_authentication</a><br>
<br>
<a href="http://drupal.org/project/ldap_provisioning" target="_blank">http://drupal.org/project/ldap_provisioning</a><br>
<br>
<a href="http://drupal.org/project/ldap_integration" target="_blank">http://drupal.org/project/ldap_integration</a><br>
<br>
Regards,<br>
<div>Sami<br>
<br>
On Fri, 2010-06-25 at 00:29 -0500, Sarah Poger Gladstone wrote:<br>
</div><div><div></div><div>> The level of integration I am looking for is just single-sign on so<br>
> that anyone with a Drupal user name and password can seamlessly log<br>
> into Moodle. Then picking a similar color scheme for the Moodle<br>
> theme so that it compliments the Drupal theme.<br>
><br>
> I am NOT planning to tie content from from one to the other, or any<br>
> other connectivity.<br>
><br>
> Some links I have looked at for single sign on:<br>
> <a href="http://drupal.org/project/moodle" target="_blank">http://drupal.org/project/moodle</a> and<br>
> <a href="http://moodle.org/mod/data/view.php?d=13&rid=2941&filter=1" target="_blank">http://moodle.org/mod/data/view.php?d=13&rid=2941&filter=1</a><br>
><br>
> Thanks,<br>
> Sarah<br>
><br>
> On Thu, Jun 24, 2010 at 1:16 PM, Sami Khan <<a href="mailto:sami@etopian.net" target="_blank">sami@etopian.net</a>> wrote:<br>
> > On Thu, 2010-06-24 at 11:06 -0400, Joe Murray wrote:<br>
> ><br>
> >> Just to echo parts of what Sami and Tim are saying: try to keep the<br>
> >> level of integration required between the Moodle and Drupal/CiviCRM<br>
> >> parts of the site to a minimum. Where it is necessary, try to make it<br>
> >> as thin and standardized as possible, or as loose and distant as<br>
> >> possible. For example, give Moodle and Drupal/CiviCRM complementary<br>
> >> but separate branding, so you don't have to replicate changes in both<br>
> >> environments, especially not simultaneously. It might even be good to<br>
> >> make one application a subdomain, eg <a href="http://crm.mycongregation.org" target="_blank">crm.mycongregation.org</a>. Also, you<br>
> >> might want to try to avoid developing integrated login by using LDAP<br>
> >> for single sign-on, though of course setting that up for Moodle and<br>
> >> Drupal / CiviCRM can be its own small kettle of fish. The objective as<br>
> >> I see it would be to avoid having to maintain middleware code that<br>
> >> would have to be kept in synch with two or more projects that each has<br>
> >> its own upgrade cycle.<br>
> ><br>
> > Agree. The problem is that there is no middle ware. Any such work often<br>
> > ends up corrupting one of the systems with tons of hacks that are not<br>
> > easily maintained. Also, it never looks like one app and expending<br>
> > resources to make it look like one is a waste of time.<br>
> ><br>
> >><br>
> >> As this is starting to become fairly complex but is really useful for<br>
> >> your vertical, you might want to make it into a SaaS offering so that<br>
> >> the setup and maintenance costs (and expertise) can be reduced through<br>
> >> scale and allocated to more customers.<br>
> ><br>
> > Agree.<br>
> ><br>
> > _______________________________________________<br>
> > consulting mailing list<br>
> > <a href="mailto:consulting@drupal.org" target="_blank">consulting@drupal.org</a><br>
> > <a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
> ><br>
><br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org" target="_blank">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><div class="im">-- <br>Sarah Gladstone<br>main: 312-970-0613<br>direct: 312-933-9275<br>skype: sarah.gladstone<br>Pogstone Inc.<br><a href="http://www.pogstone.com" target="_blank">www.pogstone.com</a><br>
<br><br>
</div></div>
<br>_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
<br></blockquote></div><br>