Currently, the plugin doesn't care at all what hostname a user used to login to a page:
When example.com and beispiel.de are both server by the same Plone instance, a user's session in example.com is terminated when the same user logs in to beispiel.de.
Sometimes, this is what you want.
And sometimes it isn't; e.g., if someone needs to compare contents in one host and another (different language versions).
Currently, I can think of two possible ways to solve this:
Use a different backend to store the no_duplicate_login cookie, adding the hostname information.
Use a different cookie name, e.g. appending a suffix.
Currently, the plugin doesn't care at all what hostname a user used to login to a page: When example.com and beispiel.de are both server by the same Plone instance, a user's session in example.com is terminated when the same user logs in to beispiel.de.
Sometimes, this is what you want. And sometimes it isn't; e.g., if someone needs to compare contents in one host and another (different language versions).
Currently, I can think of two possible ways to solve this:
no_duplicate_logincookie, adding the hostname information.