<br><br><div class="gmail_quote">On Wed, Jan 5, 2011 at 5:20 PM, antgiant <span dir="ltr"><<a href="mailto:antgiant%2BdrupalDevel@gmail.com">antgiant+drupalDevel@gmail.com</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;">
Bakery is what Drupal.org and <a href="http://groups.drupal.org" target="_blank">groups.drupal.org</a> uses for SSO. However, be warned that it doesn't play nice with the LDAP modules and if your user's clock is off by more than you session expiration amount they will only be able to log in with firefox.<div>
<div></div><div class="h5"><br></div></div></blockquote><br>Hi Antgiant, thanks a lot for your reply.<br><br>Seems that bakery module works only with subdomain that are on the same second-level domain, that is not my case... :/<br>
<br>Ideally, i need a solution also to synchronize profile fields (it's not a strict requirement).<br><br>The situation is really complicated because "username" are not unique across different sites, so probably "foobar" user of "site a" is not the same "foobar" of site b.<br>
<br>I think that OpenID solution would be better, but all subsites must be in the same time provider/producer, example:<br><br>1) I have an account on site a<br>2) I log in with my openid account of site-a to site-b<br>3) site-b asking me if i'm a new user or i already have an account to site-b, if new site will grab data from site-a to create my new account otherwise it synchronize with site-b account.<br>
<br><br><br><br><br></div><br clear="all"><br>-- <br>Paolo Mainardi<br><br>CTO Twinbit<br>Blog: <a href="http://www.paolomainardi.com" target="_blank">http://www.paolomainardi.com</a><br><br>-- Please consider the environment before printing this email --<br>