We're testing enabling checksums on our Volumes, but it looks like only the Windows client will warn if there is an incorrect checksum on a document.
Will this functionality be added to the Web Client? We're currently on 10.4.1
We're testing enabling checksums on our Volumes, but it looks like only the Windows client will warn if there is an incorrect checksum on a document.
Will this functionality be added to the Web Client? We're currently on 10.4.1
Hi Craig,
Thanks for reporting this issue. I verified that the volume checksum warnings don't appear in Web Client 10.4.2 as well and have filed a bug. It hasn't gone through the triaging process yet so I don't have a target release to report at this time.
Cheers,
Sam,
We're interested in using checksums to further enhance the integrity of our files. We have our volume locations secured via Windows file security but with using the checksums it would give us verification if anything changed outside of Laserfiche.
I'm not concerned with end-users getting warnings as they show know if something isn't correct with the document. I wish there was an easier way to validate checksums other than manually checking in the Administration Console, perhaps via Audit Trail or a way to schedule a validation?
We're working on a project where we would be storing documents which are subject to the FBI's Criminal Justice Information Services (CJIS) Security Policy and want to make sure that our data is secure and is fully auditable. So we would be using Audit Trail to be able to prove repository activity if anything ever was questioned and checksums would verify that the files haven't changed outside of Laserfiche.
Thanks for this info Craig - was quite useful. I wanted to provide you an update as well. Turns out the omission of checksum validation warnings in Web Client was intentional, as said warnings are typically not actionable by end users.
Instead, we have filed a feature request to be able to automate/schedule volume integrity checks and reports on the Laserfiche Server side. Seems like that would much more effectively address the actual goal.
Sam,
Thanks - I'll agree being able to get reports would be more useful.
Craig, I'd actually like to ask a few follow-up questions here.
Having business context around how our customers use features like this is incredibly valuable for both prioritization and future development plans.
Thanks!