Task #4666
Batch Process: User Activation: password handling
| Status: | Work Completed-End life cycle | Start date: | September 03, 2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | December 19, 2014 | |
| Assignee: | - | % Done: | 0% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
ii) Password Handling: 1st time user creation and Reset password:
RCAS - Batch Process function for User Activation and manually trigger by RCAS admin, it is use for CFO user id creation and password (1st time and reset) notification by Batch SMS and Batch Email.
Issue: i) If selected the notification is Batch SMS and Batch Email for ID creation and Reset Password. The activity did not appear in the Batch process screen.
ii) Password Handling: During send out notification for batch email or batch sms, RCAS will not be able to read or decrypt the password that has been encrypted by HSM. RCAS must regenerate the password in order to send the password to the user. However, the concern is on the password generated date, whether to follow the initial process (either create user or reset password) or during send out notification, because the password date generated will be used to check against password expiry date policy.
Propose solution for item ii:
Password Handling: The password will generate it during trigger the notification and the password generate date will be base on during trigger the notification.
New User ID creation and password:
Example: 25 Aug 2014: if user A created and selected the notification is Batch Email,
27 Aug 2014: RCAS admin submit the task in the Batch Process, user id A created on 25 Aug 2014 and password will generate on 27 Aug 2014 and send out from RCAS on 27 Aug 2014 of the notification.
Reset Password:
Example: 26 Aug 2014: If user B reset password by RCAS admin, the password yet to reset(generate).
28 Aug 2014: RCAS admin submit the task in Batch Process, user B password will reset (generate) on 28 Aug 2014 and password notification send from RCAS is 28 Aug 2014.
waiting for Bank (Azmat and Zaila) to confirm which solution.
Need to branch out and base in R1
History
#1 Updated by Anonymous almost 10 years ago
if time permited, please include in R2. let monitor later.
#2
Updated by Yap Kah Yan almost 10 years ago
- Status changed from New - Begin Life Cycle to Development / Work In Progress
Issue (i) is included in R2:
i) If selected the notification is Batch SMS and Batch Email for ID creation and Reset Password. The activity did not appear in the Batch process screen.
#3 Updated by Anonymous almost 10 years ago
for item ii) pls follow above proposol solution.
For source code review, not require to incluse all this Batch process changes.
#4 Updated by Anonymous almost 10 years ago
please do the full test and release in R2 if there has any defect can be included.
#5
Updated by Ong Wei Kuan almost 10 years ago
- Status changed from Development / Work In Progress to Internal Testing
- Assignee changed from Ong Wei Kuan to Anonymous
Has merged the change into R2.
#6 Updated by Anonymous almost 10 years ago
- Due date set to December 19, 2014
- Status changed from Internal Testing to Work Completed-End life cycle
already release to Bank in R2