2FAuth - Package Updates

Package Updates

[1.3.0]

Update 2FAuth to 5.3.0
Full changelog
The /up endpoint for health checks (#271).
A user preference to close the on-screen OTP after a predefined delay
A user preference to automatically register a 2FA account immediately after a QR code scan. When enabled, there is no need to click the Save button anymore to save the account to the database.
An admin setting to make SSO the only authentication method available (does not apply to admins). (#368).
The ability to assign a 2FA account to a specific group directly from the advanced form (#372).
A new Auth tab in the admin panel to gather settings related to authentication

Package Updates

[1.3.1]

Package Updates

[1.3.2]

Update 2FAuth to 5.3.2
Full changelog
Error asking me to log out when using multiple devices, pressing back logs me in anyway

Package Updates

[1.4.0]

Update 2FAuth to 5.4.0
Full Changelog
The links in the footer (Settings, [Admin,] Sign out) have been replaced by the email address of the logged in user. Clicking on this email shows a navigation menu containing the links that were previously visible in the footer. The former display is still available if you don't like the new one, just uncheck the new Show email in footer user option in Settings. (#404)
Administrators can now configure 2FAuth to register 2FA icons in the database (see the new Store icons to database setting in the admin panel). When enabled, existing icons in the local file system are automatically registered in the database. These files are retained and then used for caching purposes only. 2FAuth will automatically re-create cache files if they are missing, so you only have to consider the database when backing up your instance. When disabled, 2FAuth will check that all registered icons in the database have a corresponding local file before flushing out the db icons table. (#364).
The ability to export 2FA accounts as a list of otpauth URIs (#386).
Part of the content of some pages (such as the error page) could be hidden by the footer on small screens.
New otpauth query parameter for the GET operation of path /api/v1/twofaccounts/export to force data export as otpauth URIs instead of the 2FAuth json format.

Package Updates

[1.4.1]

Update 2FAuth to 5.4.2
Full Changelog
CSP has been turned off (for now) since it breaks the app under Google Chrome. (#417)
Fix XSS & SSRF vulnerabilities (thx to the XBOW team).
Content Security Policy is now available and enable by default. CSP helps to prevent or minimize the risk of certain types of security threats.\

Package Updates

[1.4.2]

Package Updates

[1.4.3]

Package Updates

[1.5.0]

Package Updates

[1.6.0]

Update 2FAuth to 5.5.0
Full Changelog
It is now possible to define custom defaults for user preferences as well as to lock the preferences from being changed by users. This feature requires a bit of configuration, a dedicated page has been added to the documentation site to guide you through the process. (#413)
A user preference to enable precalculation and display of the next OTP code.\
Don't be surprised if you don't see the next code right after enabling this option, the code fades in slowly in order to maintain good readability of the current code. (#416)
New languages: Danish, Dutch, Italian, Korean, Portuguese (Brazilian)
The version number has been removed from the footer and from the About page for unauthenticated users. (#432)
2FAuth now starts searching as soon as the user starts typing, without having to explicitly give focus to the search field. (#441)

Package Updates

[1.6.1]

Cloudron Forum