1.65.14.6 consists of four fixes that strengthen sign-in and protect sensitive information. There are no changes to how you use LabLogs, but you will be asked to sign in once after this version is deployed to your environment.

LLMB-4: The checks that confirm a sign-in is genuine were not strict enough in certain cases.

Corrective action: Sign-in verification now rejects anything it cannot fully validate. Normal sign-in, including single sign-on, is unchanged.

LLMB-5: One reporting screen did not apply the same input protections used in the rest of the platform, and error messages could show more technical detail than needed.

Corrective action: The reporting screen now uses the same input protections as the rest of the platform, and users see a general error message while the technical detail is kept in secure server logs. Normal use of the report is unchanged.

LLMB-6: In some situations, sensitive sign-in information could be written to internal system logs.

Corrective action: Passwords and session credentials are not recorded, and password-change requests are masked in the activity trail.

LLMB-52: Users signed in to more than one LabLogs environment at the same time in the same browser (for example, Production and Beta) could see an "Error checking permissions" message followed by endless loading, because the sign-in session was shared between environments.

Corrective action: Each environment now keeps its own sign-in session, and it is no longer shared with other LabLogs addresses. Being signed in to multiple environments at once no longer causes permission errors. Users will need to sign in once after this version is deployed; this is expected.

*Release date = the date a version was released into the Production environment. Each Lab Logs environment will display the release date as the date the version was deployed into that environment.