Is Quick Fields 10.3.0.81 compliant with FIPS? Has anyone be able to use it in that environment?
I'm answering my own question. No, it is not compliant. When I disabled FIPS on the workstation it ran a session to completion without error.
Sorry about the late reply. Quick Fields 10.3 relies on an older version of our OCR engine which crashes when FIPS is enabled. Bug reference ID 55406. We do not currently have a target date for a hotfix.
Installing a Laserfiche 10.4 Windows Client on the machine should update the OCR version to one that will contain the fix.
1. Are you saying that the 10.4 Windows Client CURRENTLY contains the FIPS fix?
2. Does the 10.4 Client installation of Omnipage OVERRIDE the QF 10.3 version of Omnipage? (NOTE: when installing ONLY QF 10.3, there is no evidence of Omnipage showing in the Control Panel Programs and Features).
The OCR version installed with the 10.4 Client contains a fix for the crash in NuanceLS.exe when FIPS is enabled.
Quick Fields bundles the OCR engine as a merge module (because OCR is required) while the Client installs it as a separate component because OCR is an optional component. Behind the scenes, they install the files in the same location (C:\Program Files (x86)\Common Files\Laserfiche\Batch Processor\BPOmniOCR192). The Client contains a newer version of lfomniocr.exe with the fix.
We've got it working - installed the Omnipage 19.2 from the Client 10.4 install. The customer is on Client 10.2, (and needs to stay there for now) but the Omnipage 19.2 is compatible. Now with FIPS turned on, the Quick Fields 10.3.0.81 can do Zone OCR without error.
This one took some detective work. Thanks, Miruna, for your input, which was the key to solving this. And thanks to James Walker for his hands-on work getting the install working!
Unfortunately, it is not working completely. When attempting to scan a PDF with digital signatures we receive the following error:
"Error: cannot scan 'OurDocumentName.pdf'. This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms."
I searched the Answers sight and this same error happened with WebAgent. A hotfix corrected the problem. Is there a hotfix available for Quick Fields?
Are you generating images for the PDF?
We're trying to extract text from the PDF to create metadata. We have an Zone OCR object defined so I'm assuming the answer would be yes. This is my first attempt using real documents and I've had no training. We do have the latest Omnipage OCR v19.2 installed on the same workstation that Quick Fields is on.