Mark singlesignon as abandoned
catch - May 15, 2009 - 08:36
| Project: | Shared Sign-On |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
The last commit to this project was over a year ago and there's a large number of active issues in the queue. I think it'd better for potential users of the module if we mark it as abandoned.
#1
If this is abandonned, is there any other solution to share login ?
Because as I said in my issue (#461784: Disconnection works fine but not connection), disconnection is perfectly shared between different domain, but not connection... I wish there was a way !
#2
It's not 100% abandoned. As soon as someone posts a reasonable-looking patch, I'll give them the appropriate access to do stuff to SSO. I've even done it once already, but the guy never applied the patch as far as I know.
Some Drupal people recently contacted me about the possibility of handing the project over to someone else. Discussions are still ensuing (I await their reply e-mail), but I'm very open to the possibility, depending on the person (the person I am discussing with is eminently suitable to judge these things, though).
So I guess what I'm saying is, discussions are in progress, but feel free to work on patches if you don't like what you see.
HTH,
#3
Please do not abandon this module. Some of us rely on it on our cross domain websites.
Thank you.
#4
I'll cast my vote to keep this module alive! I don't currently use it, but I'm about to start on a project that will most likely require it.
#5
If I may ask, is it compulsory to share some specific tables in the database in order for this module to work effectively?
My reason for asking is that, I already make use of domain access with a single database for all my multisites. As it stands, everything is working perfectly.
Recently, I have decided to use the shared signon module and I'm having a feeling it's going to change everything i have been working with.
I also want to know if domain access and shared sign on modules can work together without things getting rough.
Thank you.
#6
I've just discovered this module after finding that Domain Access is the way forward for my project instead of multisites. Single sign on is required and it would be terrible for this project to be abandoned when I've only just discovered it.
#7
Woh, woh, woh, woh, stayin' alive, stain' alive.
(my vote)
Seriously, though, I will have to find workarounds on too many sites (that use the domain access module) if this project bites the dust.
#8
I just started a project of 2 sites sharing users, roles, permissions... and session :P
Everything else is working up until now on my tests, but session is not. If I login on 1 site, I must login on the other; if I logoff on 1, I keep logged on the other.
I came to this module hoping to find a solution and unfortunately I read that logoff is shared but logon is not :(
plz keep it alive! if somebody find a logon solution, I will most likely use this module!
#9
I am not sure what possibilities this modules gives; haven't tested it yet. But because of I am searching for a sso-module I came to this; so I will test it.
Gyu's, if this is a potential good module for sso-features it would be horrible for the whole Drupal if it would be abandonded.
greets
Michael
#10
Hi! I do use successfully singlesignon on my site so please keep up!
drupal 6.12
Shared Sign-On 6.x-1.3 2008-May-08
and others not relevant.
#11
Lexas, I understand your problem for not finding proper help on this cause I have myself struggled to find. But there is almost no need. The solution is too easy to see ;). All you have to do is go through configuration steps in settings.php for multisite config and activate this module for every site you want common sign-on process. Don't forget to setup a "master site" at site configuration panel for shared signon module and that's it. Don't worry be happy.
#12
My vote to continue developing & supporting the module.
Please do not abandon - Need SSO.
#13
Please don't abandone the project. It's useful.
#14
Don't abandon this module, it seems very useful.
#15
Because people who use this add-on obviously have a lot to take care of, I feel like it should be second priority only to core. Plus, I got 5 on it.
P.S. - HTH: Did you try sending a follow-up email? ^^
#16
Good module .. need to carry on.. If needed I can help as co-maintainer.
#17
If someone posts sensible-looking patches to one of the problems mentioned on this site, then I'll sign them on as co-maintainer.