I 'm also very much interested in this toppic.

I tried the PUR-module but got stucked in defining the default login to be redirected to the PUR-module. I assumed that pointing server > filters > uriSecurity > clientCallback > loginForm to the page where the paragraph "Public Users: Login form" is inserted (/public-user-registration.html in my case) should do the trick.
But seems I was wrong since I got a freemarker exception:

java.io.FileNotFoundException: Template /public-user- registration.html not found. at freemarker.template.Configuration.getTemplate(Configuration.java:489) at freemarker.template.Configuration.getTemplate(Configuration.java: 459) at info.magnolia.freemarker.FreemarkerHelper.render (FreemarkerHelper.java:107) at info.magnolia.freemarker.FreemarkerHelper.render (FreemarkerHelper.java:85) at info.magnolia.freemarker.FreemarkerUtil.process(FreemarkerUtil.java: 125) at info.magnolia.cms.security.auth.callback.FormClientCallback.doCallback (FormClientCallback.java:73) at info.magnolia.cms.security.auth.callback.AbstractHttpClientCallback.hand le(AbstractHttpClientCallback.java:47) at
[ ... ]

Now can someone help me out here? What is it I need to do to get the PUR-module up, running and handling secured URIs.

I really would love to give it a try again.
So thanks for any pointers.
brgds, Thomas



On 24.04.2008, at 10:15, Vaudano Luca wrote:
Hi Will,

what is different from the features of the magnolia-PUR-module?
This module makes available a login mask, user validation, retrieve
password paragraph; and saves the user data in the JCR repository.
But I have a question about this module, if I have one author instance
and two public instance, the three JCR repositories after a user
registration could become not align.
By the way, if you are interesting, I made a module starting from
magnolia-PUR-module that saves the user data, using spring - hibernate
frameworks, in a centralized database.

Regards,
Luca

On Thu, Apr 24, 2008 at 7:30 AM, Will Scheidegger
<[email protected]> wrote:
Dear Magnolians

The subject has been discussed here several times, but there has yet to be
found a good answer. See for instance:

http://www.mail-archive.com/search?q=custom+login&l=user-list% 40magnolia.info

 We therefore suggest a Magnolia extension that gives us flexible
alternatives when it comes to the login mask. In my opinion such a
"magnolia-module-login" should allow to define rules in the configuration, which get Magnolia to display different login masks depending on the URL
that was called, e.g.

- */magnoliaAuthor/.magnolia* -> standard Framemaker Magnolia login mask

- http://customer_a.com/public/*-en.html -> display the magnolia page /public/cust_a/login-en.html (which of course should contain something like
a login paragraph)

 - http://customer_b.com/public/* -> display the magnolia page
/public/cust_b/login

 What do you think:
 Would this module be helpful for you too?
 Would you need additional/different features?
 Would you be interested in helping to develop it?
 Has someone already developed something similar?
Are the Magnolia developers by any chance already working on something
similar for the next Magnolia release?

 Cheers,
 Will

 ----------------------------------------------------------------
 for list details see
 http://documentation.magnolia.info/
 ----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to