Page History

Magnolia's Public User Registration module allows users to register an account on the public site. This page explains how to use the module to set up public user registration and protected pages that are available only to users who have registered and logged in.

The tutorial takes you through the process of:

...

You can make the components available on any  page template . The components will be used on pages Creatingpages for registration, login and related PUR tasks. 

...

...

• PUR pages: 
  • Base these pages on your PUR template. We will add the PUR components made available MakingPURcomponentsavailable above to these pages. 
  • You need one page for each PUR component, for example a registration page for the Registration form component, a login page for the Login form component etc..
• Restricted content pages: 
  
  • These are standard pages. They do not rely on the functionality of the PUR module.
  • You can base these pages on any template and you add any components.

...

• Registration: Always registration strategy enables users immediately. A user can access restricted content straight after registration. 
• Password retrieval: MailChangePasswordLinkStrategy sends an email to the user who submits the password retrieval form. A link in the email directs the user to the example /change-club-password page. 
• Default group: We create the sportstation-pur group in Setting permissions Settingpermissions (below). 
• Default role: The configuration overrides default to ensure that users assigned only the anomymous role cannot access restricted content.  

...

...

At this stage, publish the work to date to the public instance. We set permissions and test the setup Settingpermissions and TestingthePURsetup on the public site because this is where it will be used and anonymous users have different permissions on the author and public instances by default.

Publish: 

• Template MakingPURcomponentsavailable (and availabiltiy configuration, if any).
• PagesCreatingpages.
• PUR configurationConfiguringthePURmodule.

Setting permissions

On the public instance, first restrict anonymous access to content reserved for registered users and then give registered users access to this content

...

Next create a new group named after the value in the defaultRoles configuration ConfiguringthePURmodule property (sportstation-pur in the example) and assign the new role to the new group. Users in this group also need other basic roles.

...

Adding a client callback to the security filter

...

...

1. Open the restricted content page logged in as superuser and then log out by adding the ?mgnlLogout=true parameter to the URL. The restricted content disappears and the page redirects to the login form page configured in the security callback Addingaclientcallbacktothesecurityfilter.  
      
2.  Click Register in the login form, register a dummy account (using a valid email address) and then login with the new credentials. The protected page (set in the Login form component AddingPURcomponents) opens.  
      
3. Log out as the new user, click Forgotten password in the login form and enter the dummy account username and email. The link in the password reminder email opens the password reset form page (set in passwordRetrievalStrategy configuration ConfiguringthePURmodule) where you can choose a new password.
        
4. Log in to admincentral and launch the Security app to verify that the dummy user is assigned to the group defined in the defaultRoles configuration ConfiguringthePURmodule.