Best practices for sharing members database between different portals

There is no good way to really handle this between domains and keep the
user logged in. I doubt there are any real "best practices" on this.
If you're disparate, you might be able to use some tricks to make it
work, but all in all, I don't think it's a very easy thing. Cookies &
sessions just don't span multiple domains!

-Galen


On Dec 9, 2003, at 1:26 PM, Tariq Murtaza wrote:

> Dear All,
>
> Please comment on Best Practices for sharing members database between
> different portals.
>
> Suppose we have 3 portals running on different networks.
> Assignment is to make a single Login/Pass for all portals, means once
> LogedIn in one of the portal, could able to access the other portals
> without loging In.
> Constraints are, every portal have different Database structure and
> also have different Global / Session variables.
>
> Please share your experience and which approach is the best practice.
>
> Regards,
>
> TM

Dear All,

Please comment on Best Practices for sharing members database between
different portals.

Suppose we have 3 portals running on different networks.
Assignment is to make a single Login/Pass for all portals, means once
LogedIn in one of the portal, could able to access the other portals
without loging In.
Constraints are, every portal have different Database structure and also
have different Global / Session variables.

Please share your experience and which approach is the best practice.

Regards,

TM