You need to look at the PUR, or public user registration module. http://git.magnolia-cms.com/gitweb/?p=modules/public-user-registration.git;a=summary
The real issue you're going to have to contend with is authorization. Sure, Shibboleth can protect a page as long as you have the policy agent installed onto your application server, but you won't have granular controls on what they can access unless you make Magnolia aware of it. For that, I would recommend that you use an LDAP to store your users for Shibboleth, then make use of Magnolia's LDAP module (er, do you have an enterprise license for magnolia?). That will let you make use of your LDAP groups for authorization, but shibboleth will do the authentication. It requires a little creativity. We just did this with Open AM and Open DJ - though we could leverage the LDAP module thanks to our enterprise license to make the development go a lot faster. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=8a808b5f-a23d-4fad-8ceb-88591de5990b You are invited to Magnolia Conference. Less than a month to go! Register now: http://www.magnolia-cms.com/conference/register.html ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
