It would be great if aegir could support the easy creation of master and client single-sign-on sites that make use of the Single Sign-on module. Some reason's why this would rock:
1. It involves multiple drupal sites (aegir's forte)
2. Setting up single-sign-on is non trivial right now - it involves modifying settings.php, making sure your mysql database permissions are set correctly, and copying a key across sites.

How rocking would it be if aegir could do all the heavy lifting of the above tasks, and then display a synopsis of which sites are masters/clients in the aegir dashboard. Very very rocking.

Comments

phayes’s picture

phayes commented
Category: feature » bug

Updating this to a bug:

Since aegir overwrites settings.php it kills single-sign-on everytime a site is verified.

anarcat’s picture

anarcat commented
Category: bug » feature

That's not a bug report.

If you want Aegir to write something special to settings.php, you need to hook into the template by writing a drush/provision module. It's perfectly possible to do that right now so that's not a limitation of Aegir.

You will however run into problems with that module because it uses shared tables. i would recommend using something like the Bakery module that doesn't require shared tables.

anarcat’s picture

anarcat commented

See also #494446: allow shared tables between sites and #556598: $db_prefix not handled in migration.

adrian’s picture

adrian commented
Status: Active » Closed (duplicate)

Duplicate of #462790: enable SSO in deployed sites