Before starting

Before starting the upgrade process, with 1.2.0-M1 running, perform the following actions either via REST or admin console:

1. Create a boolean configuration schema passwordReset.allowed
2. Create a boolean configuration schema passwordReset.securityQuestion
3. Create a notification with 
   1. mail template requestPasswordReset
   2. event [CUSTOM]:[]:[]:[requestPasswordReset]:[SUCCESS]
   3. user filter token!=$null 
   4. recipients: flag only Include users matching About
4. Create a notification with 
   1. mail template confirmPasswordReset
   2. event [CUSTOM]:[]:[]:[confirmPasswordReset]:[SUCCESS]
   3. user filter token!=$null
   4. recipients: flag only Include users matching About

Source changes

POM

In the root pom.xml:

...

INSERT INTO Entitlement VALUES("SECURITY_QUESTION_LIST", NULL);
INSERT INTO Entitlement VALUES("SECURITY_QUESTION_READ", NULL);
INSERT INTO Entitlement VALUES("SECURITY_QUESTION_CREATE", NULL);
INSERT INTO Entitlement VALUES("SECURITY_QUESTION_UPDATE", NULL);
INSERT INTO Entitlement VALUES("SECURITY_QUESTION_DELETE", NULL);

Other changes (via REST or admin console)

...

1. mail template requestPasswordReset
2. event [CUSTOM]:[]:[]:[requestPasswordReset]:[SUCCESS] 
3. user filter token!=$null 
4. recipients: flag only Include users matching About

...