[consulting] "Political" question about single login

[Jason Smith]

domain access is a fantastic module, but it is a far reaching one. Some
things it handles very well, some .... not. It is a really comprehensive
module, but it cannot catch every use case or handle all third party
modules. So if you don't fit in the groove, prepare for some work. What you
are describing is more of a side effect of domain, not it's central use.

It will handle 1. easily enough, but not 2. Personally, I would use OpenID
as it would be more targeted to your needs.

On Wed, Mar 31, 2010 at 9:20 AM, sivaji j.g <sivaji2009 at gmail.com> wrote:

>
>
> On Wed, Mar 31, 2010 at 7:40 PM, Audrius Naslenas <
> audrius.naslenas at gmail.com> wrote:
>
>>
>> What is the best way to make single login solution with:
>> 1. Single and preferably only one login/register place on "central" site
>> of network
>> 2. Different usernames (display names) and configurable user profile data
>> on each site
>>
>
>> For now, I am not in a rush to sell soul to Facebook Connect, (well even
>> this module does not have 100% needed features) what are the other viable
>> choices?
>> Some other LDAP based solution, not even Drupal itself? CAS? Single Sign
>> On module? OpenID + supporting modules?
>>
>
> Try Domain Access module http://drupal.org/project/domain
>
>
>>
>>
>>
>>
>
> --
> Thanks
> Sivaji
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20100331/02f092f6/attachment-0001.html