Cookie for multiple tld domains

[Floezen]

@corbyboy

If you can let us know what you are trying to achieve maybe somebody can give you some more specific ideas on what you should do.

Yes. Let me kindly answer with a quote of my own:

@Floezen

[…]
My CMS is in German and English, but I want to strictly separate them by tld.
[…]
So in my case a user, that is for example is already logged in might want to change the language. (Would usually occur for German users, that found the English content first, log in, and than want to change to German).

Regards
Flözen

[AnthonySterling]

Would a happy compromise be the auto-completing of the user-name field and prompt for their password?

For instance, the user selects a preference to use the .de domain, you pop-up a modal window (al la lightbox?) which is actually generated by the .de domain asking for their password.

“Please enter your password to save preferences…”

As they submit, they actually login to the .de domain.

[crmalibu]

Do a search for single sign on.

[felgall]

@corbyboy

It depends on what you are using this for.

The OP gave a full explanation of that back in post 7 of the thread.

One possible solution would be to use the 1x1 images to generate the cookies and just store a token in the cookies (same in each). When they login the token from the current cookie gets copied to to the database to indicate that the browser using that token is logged in. You simply test if the current token is assigned to someone already logged in before so as to know when to skip asking for a login because they already are. You then start adding as many additional checks to that in order to minimise the possibility that the cookie containing the token has been copied.

As a completely different alternative, how about storing their language preference along with their login details and have the login window swap them to the correct domain before it stores the cookie. That way the cookie need only be stored on the one domain.

[Floezen]

OK, thank you all for your input.

I had expected it to be a one-minute task…
But at least there is a solution, that should be done within an hour - thats fine too.

Everything else I will look into, next time I’m bored… :goof:

Regards
Flözen

[AnthonySterling]

@felgall

The OP gave a full explanation of that back in post 7 of the thread.

One possible solution would be to use the 1x1 images to generate the cookies and just store a token in the cookies (same in each). When they login the token from the current cookie gets copied to to the database to indicate that the browser using that token is logged in. You simply test if the current token is assigned to someone already logged in before so as to know when to skip asking for a login because they already are. You then start adding as many additional checks to that in order to minimise the possibility that the cookie containing the token has been copied.

As a completely different alternative, how about storing their language preference along with their login details and have the login window swap them to the correct domain before it stores the cookie. That way the cookie need only be stored on the one domain.

Did you actually read this thread?