This could be useful for website where magnolia security is used also on the public instance:
at the moment you can only use a static page or a freemarker template for the login page, but not an existing page managed by magnolia. Having a cms-managed login page is a common requirement.
I already have some code for this that I will try to integrate soon, these are a couple of details about how it works:
- the configuration for the login page doesn't replace the existing one, but it's an additional entry
- the page is only displayed on public servers and not for the ./magnolia/* path (if the page in the website repository is not configured properly don't prevent administrators to login at all!)
- the difficult part: when a secure uri is requested, the login page is displayed. After the login the user is redirected to the same page he was trying to see before authentication (with all the parameters submitted originally, and also if he had to navigate across more bages before login
for example after a self registration