2 Factor Authentication

Version 2.1.0b1: - Change: Authentication codes are refused once they are older than 60 minutes, instead of staying valid until the next cleanup removed them - Change: The authentication code is only accepted in the browser that entered the password; the email link opens the code form there, and on another device shows the code to enter on the device where you signed in - Change: A login allows 5 wrong codes, after which the password must be entered again; a new password login replaces any earlier pending login - Change: Codes use 6 easy-to-read characters (no 0/O/1/I) and can be entered in upper or lower case - Change: "resend code" works only in the browser that entered the password, at most once a minute, and sends to the account's current email address - Change: After the code is entered the session is built from the current account, and the login is refused if the account was deactivated, blocked or unvalidated, its password changed, or maintenance mode was turned on since the password was entered - Change: Turning on 2 Factor Authentication for an account, or adding groups to "Required For", removes the affected users' existing remember-me login cookies; a cookie made after a completed 2FA login still logs in without a code - Change: After the code is entered, the Quota "Login Page" setting is honoured like a normal login (otherwise the user goes to their profile as before) - Change: 2 Factor logins follow the User Accounts "login_activity_log" setting and use the same Activity Log text as a normal login - Bug Fix: the timeline "has logged in" entry was created when the password was entered (even if the code never was) and again after the code Version 2.0.0: - New: Module updated with a new interface for entering the authentication code - Change: Updated view structure to support new updates in Jamroom Core 6.5.12+ - Change: User is redirected to their profile after login versus any "saved" location Version 1.1.4: - Bug Fix: 2 Factor Authentication checkbox may not show even if enabled in Quota Version 1.1.3: - Bug Fix: 2 Factor Authentication checkbox could show on non-admin user settings to admin users Version 1.1.2: - Bug Fix: Redirect to 2 Factor code form on login could happen even if "Required For" was disabled - Change: 2 Factor Auth checkbox is locked in User Account for master admins if "Required For" is enabled Version 1.1.1: - Bug Fix: If "Required For" was not configured it could return an invalid required group Version 1.1.0: - New: "Required For" global config to force-enable 2 factor authentication for User Groups - Change: Generated email codes are only valid for login for up to 60 minutes Version 1.0.5: - Change: Updated to work with new Recycle Bin functions found in Jamroom Core 6.2.0 Version 1.0.4: - Bug Fix: Two Factor sessions not being removed when Developer Tools "Reset System" tool is run Version 1.0.3: - Bug Fix: "Continue URL" may not appear correctly in authentication code resend email Version 1.0.2: - New: authentication email now includes clickable link to directly log in Version 1.0.1: - "Remember Login" now works correctly with 2 factor authentication enabled Version 1.0.0: - Adding new Changelog - Initial Release