Conversion to user account system

This page provides instructions to convert existing users to accounts so you can use the account system. Please read more about the user account system first if you haven't done so already. Read more about: User accounts.

Older applications uses field roles to define which classes and fields play a role in user identification such as  “Login name”, “Password” en "User group". These field roles are no longer used by the account system (unless you use a form of 'direct' login). Here is how to do a conversion.

• Go to your user class(es). On the tab 'Other settings' you will find the field “Email field for account”. Select the email field that currently has the field role 'login name'. The account system requires at least a valid email address and uses this as the primary login name.
  
  
• If you want your application to also support existing login names, you have to check ´Allow login name' in the blueprint properties. At the moment the account system does not support creating new accounts with a login name.
  
  
• Reload the blueprint.
  
  
• In the backstage, go to 'Deployment > Conversions > Create accounts...'. Run this conversion on all servers/database you need (for example develop and production)
  
  
• After the conversion has been run, you may remove the old field roles.
• It is possible to set the improvement step "Email for account is read-only".

Notes

Read carefully!

• The password strength as defined for the user group will be strictly respected in the account system. This was not always the case in the old system. Users with passwords that are not string enough will be prompted to change the password directly after login.
  
  
• The account system does not support automatic login using only request parameters. Please contact CrossmarX if you require such a solution.