I see that I am not alone, and have the requirement for single signon (or at least a simpler signon experience) for a network of sites I am developing with the new Aegir 1.x

NOTE: I do actually require cross-domain single-signon, but there are no projects alive or supported that fit cross-domain. Sadly the Dev Seed Osso project was never contributed and hasnt been touched for a while.
https://github.com/developmentseed/osso_provider and https://github.com/developmentseed/osso_relying haven't been touched for almost a year

so, back to Bakery..

with the launch of D7, Aegir 1.x and a pretty powerful Bakery module, I wonder if there is enough interest to do something with Bakery and/or Aegir to allow master-slave type relationships for user signons

way back in 2009 anarcat left a single-signon note to himself
http://drupal.org/node/462790#comment-4442440

more recently, seth.vincent - who is porting Aegir's front-end from D6 to D7 for the Google Summer of Code - asked the Aegir-Bakery single-signon question http://drupal.org/node/1096660

a previous feature request for Aegir single signon from phayes http://drupal.org/node/608918

there has been some promising work with Hostmaster modules like Hostmaster Plus allowing Aegir API development http://drupal.org/project/hostmaster_plus

and a single-signon question by markwk http://groups.drupal.org/node/140874

thanks

Comments

niccolox’s picture

niccolox commented

posted a Discussion item http://community.aegirproject.org/discuss/single-signon-or-aegir-support...

coltrane’s picture

coltrane
he/him
commented
Status: Active » Closed (duplicate)

Woh, please don't open another issue for this. Closing this as a duplicate of #1096660: D7 bakery with Aegir

niccolox’s picture

niccolox commented

this issue has a bigger scope than D7

will check D6 stock, and D6 distro's like Managing News, Open Atrium, Drupal Commons, Open Scholar etc and update issue, perhaps enough to re-open it

tah

-N

niccolox’s picture

niccolox commented
Version: 7.x-1.x-dev » 6.x-1.0-alpha2
Status: Closed (duplicate) » Needs review

this is happening on D6 versions too inside Aegir

i.e. inside Aegir using D6 stock get the access denied and page not found errors

outside Aegir, using D6 stock, Bakery works fine

also, the install.txt says to update the settings.php while the documentation page does not mention settings.php

on D6 outside of Aegir I installed by the documentation page http://drupal.org/node/1113208 and Bakery worked

on D6 inside of Aegir, I followed the doc page above and Bakery failed

lelizondo’s picture

lelizondo commented
Status: Needs review » Closed (duplicate)

I just found this issue, I don't know why it needs review. There's no patch.

niccolox’s picture

niccolox commented
Status: Closed (duplicate) » Needs work

I mis-understood, I thought "needs review" meant it needs review for some kind of plan, didn't realize needs review means "code review"

so, would prefer it if "needs work" and it stayed open

but whatever, I'm over pushing this one

lelizondo’s picture

lelizondo commented
Status: Needs work » Closed (duplicate)

I might understand why are you doing this. You think that this issue is not a duplicate of #1096660: D7 bakery with Aegir because this is a D6 issue. But trust me, if there's a patch for D7, and is possible to backport it to D6, it will be done by someone eventually, but that will happen at #1096660: D7 bakery with Aegir, not here.

As a maintainer myself of other modules, I can tell you that re-opening duplicate issues is not cool. BTW, "needs work", is when there's a patch that the maintainer will not commit because is not a working code or at least is not ready to be committed.

niccolox’s picture

niccolox commented

this is very frustrating.

if all my issues didn't get presumptuously closed i might be happy with a slightly mis-categorized ticket i.e. duplicates etc

I wrote this ticket "Aegir support for Bakery (or Bakery support for Aegir)" because http://drupal.org/node/1151020 is specific to D7

both tickets have been closed as duplicates (of each other?)

I took the time to document a number of inter-related issues, created an issue to try to bind a number of them together, I kept the issues alive when they where mistakenly closed and now I am getting "you are being rude"

no wonder people are drifting to github

coltrane’s picture

coltrane
he/him
commented

@niccolo,

While the title of the other issue was specific to Drupal 7, the point of it was making Drupal work with Aegir, which was also the point of this issue (regardless of Drupal version) so as lelizondo points out that work can (and should) happen in one issue. That's the reason this one was previously closed as a duplicate. The title of the other issue should have been less specific and the version field used to denote the focus on Drupal7. Once working for D7 it could have been backported in that issue to Drupal 6. Separate issues for core versions isn't necessary.

greggles didn't close the other issue as a duplicate of this issue, he closed it because the Bakery issue queue is not the place to discuss making a cross-domain SSO solution that explicitly works for Aegir.

If there is some bug or feature that can be accomplished within the Bakery module to support SSO (on the same domain) with Aegir than this issue can be re-opened, otherwise (as it sounds like discussion has resulted on) we ask that you kindly take your work on a cross-domain SSO solution for Aegir elsewhere.