AndrewPoppe / REDCap-PRO

REDCapPRO is an external module for REDCap that enables Patient Reported Outcomes in a manner that complies with regulatory stipulations.
GNU General Public License v3.0
4 stars 3 forks source link

Process Flow for MFA and Create account with Auto Enroll #102

Closed dheskettmgb closed 3 weeks ago

dheskettmgb commented 1 month ago

Describe the bug Using REDCapPRO v2.4.0, and using MFA, settings both in system config and in project. ( REDCap v14.0.16 and v14.0.31 )

Adding a new participant with auto enroll.

Starting with the public survey link, and going through the Login and Create, filling out the steps,

At the page, Password Successfully Set, the user might be at a loss for the next step.

It is here, where we seem to be off from what expected flow, that we recall, before, had operated as we had expected.

We should be continuing to the survey page, via the MFA process.

We expect to get to 2-Step Login with the 6-digit security code page, and then to the survey page.

However, we are at the Password Succesfully Set and the user not instructed what to do next.

Are we misunderstanding something or forgot how it worked, in how the process flow should go?

To Reproduce Steps to reproduce the behavior:

  1. Setup: REDCapPRO v2.4.0 (S0.png) ( REDCap v14.0.16 and v14.0.31 ) and Using MFA, settings both in system config and in project (S1.png, S2.png, S3.png), checked.

  2. Adding a new participant with auto enroll.

Process:

  1. Starting with the public survey link, gets us to the Login ( 1.png ), and using Create one link,

  2. takes us to Create Account ( 2.png ), filling out ( 3.png ), giving Account Created ( 4.png ) and check your email.

  3. In the system, user is created, ( 5.png ), and

  4. checking email ( 6.png ), click the link to create password ( note using incognito to avoid the login logout of admin in browser ),

  5. click here ( using go to incognito page ), takes us to Create Password ( 7.png )

  6. hit Submit, takes us to Password Successfully Set ( 8.png ).

  7. At the page, Password Successfully Set ( 8.png ), the user might be at a loss for the next step.

  8. We should be continuing to the survey page, via the MFA process.

  9. We expect to get to 2-Step Login with the 6-digit security code page,

  10. Login ( 10.png ), fill in fields ( 11.png ), click Login,

  11. get to 2-Step Login ( 12.png ),

  12. check the email ( 13.png ) get the code,

  13. enter the code on 2-Step Login ( 12.png ),

  14. get logged in and MFA, to get to survey page ( 14.png ). ( which here is just a dummy public survey page )

NOTE: Either running on our DEV server or using a local host programmers dev server, running the above steps.

Expected behavior Expecting:

  1. At the page, Password Successfully Set ( 8.png ), next

  2. We expect to get to 2-Step Login with the 6-digit security code page,

  3. enter the code on 2-Step Login ( 12.png ),

  4. get logged in and MFA, to get to survey page ( 14.png ). ( which here is just a dummy public survey page )

Screenshots Please see screen shots.

Settings pngs: S0, S1, S2, S3. s0 s1 s2 s3

Process pngs: 1,2,3,4,5,6,7,8,9,10,11,12,13,14

1 2 7 8 3 9 10 4 11 5 13 12 14 6

Desktop (please complete the following information):

Smartphone (please complete the following information): NA

Additional context NOTE: Either running on our DEV server or using a local host programmers dev server, running the above steps.

AndrewPoppe commented 1 month ago

@dheskettmgb I think what you're seeing is the intended flow, with the rationale being that the user has already been required to check their email and click the magic link in order to set their password. So sending a second email for MFA seemed redundant. However, they would not have the opportunity to set up MFA with an authenticator app, so I tend to agree that the flow should be changed.

I will change it to require MFA after they set their password if they are creating a new account.

AndrewPoppe commented 1 month ago

Submitted v2.5.0 to REDCap Repo

AndrewPoppe commented 1 month ago

v2.5.0 was approved in REDCap Repo. @dheskettmgb when I hear confirmation that this meets your needs I will close this issue.

AndrewPoppe commented 3 weeks ago

Closing stale issue