v2.5.0

• New Feature: If project-level override of the timeout time due to inactivity feature is allowed, then it is now possible to set a maximum timeout time.
• Change: Inactivity Timeout now applies to the Survey Queue page in addition to Survey pages
• Minor Bug Fix: A bug was fixed in which, if a url to the REDCapPRO login page for a particular survey was pasted into another browser context, then participant would not be able to progress to that survey despite a successful login.

Full Changelog: 2.4.1...2.5.0

v2.4.1

• Critical bug fix: Fix for #100 and #101- When using the Survey Queue the module could fail to log the username of the participant. This has been fixed.

Full Changelog: 2.4.0...2.4.1

v2.4.0

New setting: Ability to set project-level timeout time for inactivity. If enabled at the system level, then an option will appear in the project settings to set a timeout time for inactivity that applies only to that project (overriding the system setting).
Change: If the timeout time (whether set at the system or project level) is less than or equal to the warning time, the warning time is set to 30 seconds less than the timeout time.

Full Changelog: 2.3.0...2.4.0

v2.3.0

• Medium security fix: Patched a vulnerability in which a Monitor staff member with knowledge of how the EM functions could manipulate a request to the server in such a way as to obtain participant identifying information. This vulnerability was introducted in REDCapPRO v2.0.0
• Change: The module now requires a v3 key pair in order to use Google reCAPTCHA to protect the self-registration form. This means the same key pair that REDCap uses to protect surveys can no longer be used with REDCapPRO.
• Minor bug fix: Added translations for some notification popups that were erroneously not translated before.

v2.2.1

• Minor change: When using an Authenticator App for MFA, the module will now use the participant's REDCapPRO username instead of their email address as the account name. This prevents confusion for participants who are enrolled in studies that do not allow an email address to be used for log in, and it is generally better since email address can be changed.
• Minor bug fix: Added translation for text on the login page. This text was mistakenly not translated in previous releases.

Full Changelog: 2.2.0...2.2.1

v2.2.0

• New Feature: Multifactor Authentication using an Authenticator App such as Google Authenticator or Microsoft Authenticator
• Change: 2FA will not be required for any action that already incorporates a magic link being sent to a participant's email address. Access to the link counts as 2FA.

What's Changed

• Enable mobile 2FA Authenticator App by @AndrewPoppe in #95

Full Changelog: 2.1.3...2.2.0

v2.1.3

• Minor Change to UI Text: Updated a typo in the Project Settings description of the API setting and included a link to this repo's README for further information about usage

Full Changelog: 2.1.2...2.1.3

v2.1.2

• Major Bug Fix: Issues around DAGs and project UI. In projects without DAGs defined, the manage participants page was broken. See #93

Full Changelog: 2.1.1...2.1.2

v2.1.1

• Minor Bug Fix: The code did not immediately return under certain situations, leading to erroneous error messages in the log.
• Minor Security Fix: Added more thorough validation of the reCaptcha value used to construct the validation URL

Full Changelog: 2.1.0...2.1.1

v2.1.0

• New feature: Self-registration
  This feature allows participants to create their own REDCapPRO account from a link on a survey's login screen.

• The feature is controlled by a system-level setting

• It must also be enabled in a project to take effect

There is also the option for the participant to be auto-enrolled in the project upon a successful registration.

reCaptcha is built in to the self-registration process, with configuration in the Control Center.

What's Changed

• Allow participant self-registration #83 by @AndrewPoppe in #91

Full Changelog: 2.0.1...2.1.0