The motivation for #5, "Hostname sensitivity" is the problem that you can't be logged into the same site via two different hostnames, even if both browser windows share the same session data.
Perhaps there is a better idea.
We could implement a whitelist of IP addresses / ranges which will be completely ignored by the plugin.
This might be useful e.g. for PDF creation facilities (pdfreactor.plone) which call back our site to create PDF documents or screenshots.
We could implement a whitelist of usernames which will be completely ignored by the plugin.
This would be useful for persons who need to access our site via two different hostnames synchroneously.
We could implement a possibility to whitelist the current user herself for a limited time (e.g. several hours).
This would require a dedicated permission which (obviously) would only be granted to few users.
Administrators would need to be given a UI to clear the whitelist.
Permitted users should be given a UI to renew the whitelisting or to terminate it.
The motivation for #5, "Hostname sensitivity" is the problem that you can't be logged into the same site via two different hostnames, even if both browser windows share the same session data.
Perhaps there is a better idea.
Administrators would need to be given a UI to clear the whitelist. Permitted users should be given a UI to renew the whitelisting or to terminate it.