THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Table of Contents | ||||
---|---|---|---|---|
|
Before starting
Before starting the upgrade process, with 1.2.0-M1 running, perform the following actions either via REST or admin console:
- Create a boolean configuration schema
passwordReset.allowed
- Create a boolean configuration schema
passwordReset.securityQuestion
- Create a notification with
- mail template
requestPasswordReset
- event
[CUSTOM]:[]:[]:[requestPasswordReset]:[SUCCESS]
- user filter
token!=$null
- recipients: flag only
Include users matching About
- mail template
- Create a notification with
- mail template
confirmPasswordReset
- event
[CUSTOM]:[]:[]:[confirmPasswordReset]:[SUCCESS]
- user filter
token!=$null
- recipients: flag only
Include users matching About
- mail template
Source changes
POM
In the root pom.xml
:
...
Code Block | ||
---|---|---|
| ||
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"); |
Other changes (via REST or admin console)
...
- mail template
requestPasswordReset
- event
[CUSTOM]:[]:[]:[requestPasswordReset]:[SUCCESS]
- user filter
token!=$null
- recipients: flag only
Include users matching About
...
, NULL); |