We're delighted to present the latest updates and enhancements to MBioLIMS. This page describes the new features and changes we've made to give you an even better experience. Find out what's in store for you in this version and how it can benefit your use.
Two-factor authentication
-
Administrators decide whether to enable two-factor authentication.
-
New two-factor authentication: in addition to their password, users enter a 6-digit code generated by an authenticator app (Google Authenticator, Microsoft Authenticator…).
-
10 single-use recovery codes are provided at pairing, in case the phone is lost.
-
Trusted devices: "Remember this device" avoids re-entering the code on a known computer, for a period set in the security policy (30 days by default). Devices can be revoked at any time.
-
Users can change their authenticator app themselves; an administrator can reset an account's two-factor authentication.
-
SSO (CAS, SAML) sign-ins are not affected.
Connection history
-
An account record shows its last ten sign-in attempts, successful or not, with the authentication mode used.
-
New Administration > Connection history screen, with filters and exports. The history is kept for 12 months by default.
User account
-
The "My account" page and the account record have been redesigned with a shared layout, in two tabs: Personal Information and Security.
-
Updating your preferences no longer requires your password.
Visit types
-
A visit type can be made unusable: it is no longer offered when creating visits or in configurations (workflows, eCRF, kits). Existing visits are unaffected.
Custom Fields
-
Simpler UI mode for conditions: a reference list appears only once in the "Field" selector, and the "Value" field adapts to the selected type (list of entries, True/False, declared values…).
API (v2)
The scope of the v2 API keeps expanding across the 26 versions.
-
New endpoints: visits (including deletion), consents, creation and update of samples with their tubes, assay types, temperature sensors (sensors, measures, alarms).
-
For technical details, see the list of V2 endpoints available in the application.
Compatibility change
-
If you use the v1 API with a login and password, this connection will no longer work for a user account subject to two-factor authentication. Use an authorization code instead, created from “My account”.
Resolved issues
-
An oversized or negative measure (entered or calculated) is rejected with a clear message instead of a technical error, including in visit imports.
-
Files attached to quantifications, assays and transformations no longer disappear after a restart.
-
Regenerating an API client's secret no longer clears its studies.
-
Protected fields used as API filters are no longer written to the logs.