Kofax License Could Not Be Checked

54 views

Skip to first unread message

Terresa Cherrie

unread,

Aug 3, 2024, 4:22:17 PM8/3/24

to weybetdiame

We recently upgraded to Acrobat DC. We have documents that have been digitally signed. Now when someone else opens them it says "The validity of the document certification is UNKNOWN. The author could not be verified." I've read up as much as I could (didn't know anything about them except how to sign a doc with one) and I've checked several things and can't find the problem. When I go to the certificate viewer it shows that we have a Certificate Authority. I read on another post that the latest Acrobat/Reader version enforce "Extended Key Usage" (EKU) attribute in the signing certificate. I checked that out and the OID (not sure what that stands for) that permit signing has five things: server authentication, client authentication, code signing, email protection and TimeStamping. It says in the Revoation tab "The selected certificate does not chain up to a certificate designated as a trusted anchor (see the Trust Tab for details). The result is that revocation checks were not performed on this certificate." It seems that I could "Add to Trusted Certificates" but we've never had to do that before, why now? Not to mention it advises me that I shouldn't do that. Please help. Thanks! Let me know if you need anything other information to trouble shoot.

Make sure that you trust the root of the certificate chain (only if you really-really trust it!). Right-click on the signature (either the signature field or in the Signature Panel on the left), select "Show Signature Properties.." in the drop-down list and then "Show Signer's Certificate". You'll see the trust chain in the left-hand panel of the "Certificate Viewer" dialog (if the signing certificate is self-signed it will be the only one in the chain). Select certificate in the chain that you trust (if you trust any) and click the "Trust" button on top of teh right-hand part. Then select the trust level and click "Add to Trusted Identities" button. Be extra careful to trust self-signed signing certificates.

Please help me also. I purchased this certificate through identrust and it is valid and I trust my signature. But the signature should be trusted on any computer that it is sent to. I had to import this certificate from my laptop because I installed it there initially but I don't use that laptop often. So now on my desktop its showing this error and my clients are questioning why its giving this error. I tried to trust it on my own computer but then it has a revocation error. saying it was not performed because it doesn't chain up to a trusted anchor. What does this mean in laymans terms? Please explain it to me like I'm a child without the confusing tech language. If its an error I can't fix because it was imported let me know. If I can fix this so that my clients see the green check mark, please help. Thanks!

Bottom line: you need to get a key that is trusted by Adobe in its Adobe Approved Trust List. While Identrust is on the AATL, you need to buy the correct digital certificate. The cheaper certificates will not automatically validate on Adobe. You will need to buy the digital certificate in the second Identrust link that I've provided.

Both batch classes (shown in the figure below) are set up to support the standard required Oracle Content Server check-in parameters. In addition, the batch class ScansForOracleUCMParameters illustrates how a batch class can be configured for optional Oracle Content Server parameters, such as Release Date, Expiration Date, and so forth.

Like all Kofax Capture batch classes, these Oracle Content Server batch classes are constructed using field types, index fields, form types, and document classes, which are described in the following sections.

Folder classes define the properties of folders for a batch class. Batches are a collection of pages, documents, and folders that are organized into a hierarchy that you define. As with other elements of a batch class, you can create, edit, and delete folder classes.

In addition to organizing your documents within Kofax Capture, the real advantage to using folders comes after the documents have been released from Kofax Capture. If you ensure that the folder hierarchy in Kofax Capture matches (as closely as possible) the hierarchy used by your document management software, you can more easily import those documents into your third-party software.

Folders are created and filled with documents as the documents are processed through the Kofax Capture workflow. You can create folders manually (with batch editing), or you can allow them to be created automatically in accordance with rules you define. Likewise, you can place documents into folders manually or automatically.

Pages can be added to documents, and documents can be added to folders. Folders can be added to other folders (nesting) up to 32,000 levels. However, loose pages cannot be added to a folder (although you may have loose pages at the root level of your batch, they must be placed into a document before they are added to a folder).

Installing and configuring the Kofax Capture release script sets up specific Kofax Capture field types, which are shown in the figure below. These field types are in turn used to define index fields in the sample document classes: ScannedDocsForOracleUCM and ScannedDocsForOracleUCMParam. When defining new index fields, you may use these field types, or create additional field types as needed. See "Setting Up Field Types".

Installing and configuring the Kofax Capture release script as described in Section 2.3, "Installing Kofax Capture Export Connector," and Section 2.4, "Configuring Kofax Capture," sets up the following sample Kofax Capture document classes:

The Document Class Properties dialog is displayed. For examples of the dialogs for ScannedDocsForOracleUCM and ScannedDocsForOracleUCMParam, see "ScannedDocsForOracleUCM" and "ScannedDocsForOracleUCMParam".

The ScannedDocsForOracleUCMParam document class includes "core" index fields that are mapped to Oracle Content Server standard required check-in parameters, plus additional "example" index fields that could be mapped to Oracle Content Server optional check-in parameters using the CHECKIN Parameters Editor (see "Accessing CHECKIN Parameters Editor").

Each of the Oracle Content Server document classes is configured with the index fields listed in the table below. The index fields that are defined for both document classes (Content ID, Type, Title, Author, and Security Group) are mapped to Oracle Content Server parameters that are required for successful check-in of documents to Oracle Content Server.

The additional index fields defined for ScannedDocsForOracleUCMParam are provided in the document class for illustration purposes only. They are examples of index fields that might hypothetically be mapped to Oracle Content Server parameters using the CHECKIN Parameters Editor.

The form types (SimpleForm and SimpleFormParameters) are provided for the Oracle Content Server document classes because at least one form type must be defined for a document class. Since a form type defines a unique form, you will set up your own form types to meet the needs of your specific application.

Use the Index Storage tab to set index values for the batch class. The Kofax Capture release script establishes assignments for the required information field items found in an initial Oracle Content Server installation. The values assigned to the index fields are supplied from the Validation module during Kofax Capture batch processing.

Select a Multipage TIFF output file type when you have more than one TIFF image in a batch, and you would like to have all of those images bundled together and checked into the Oracle Content Server as one content item.

When you select TIFF, JPG or PCX, the first graphic in each batch is checked into Oracle Content Server. Because of this, you may want to use Multipage TIFF (see "Selecting Multipage TIFF Output File Types") if you have more than one graphic in a batch. Alternatively, you could ensure that each batch contains only one graphic.

When you choose to release images as Adobe Acrobat Capture PDF (from Multipage TIFF), you then use Settings button to specify Adobe Acrobat Capture workgroup hub, watched folder, workflow, and other settings.

The Server tab on the Oracle Content Server Release Setup dialog is used to specify settings for Oracle Content Server URL, user name, and password; to select options for workflow and primary/alternate file check in formats; and to access the CHECKIN parameters editor.

There are two drop-down menus available-one for the primary file and one for the alternate file. Within each menu, you can choose: Image, Kofax PDF, Adobe Acrobat Capture PDF, or OCR full text. The Alternate file menu also includes a [None] option in case you do not want to check in an alternate file.

If the Allow Workflows check box is selected, the content item identified by the user (on the Validation dialog) must be checked out of Oracle Content Server before Kofax Capture initiates check in. If the content item is not checked out, the check in will fail with an error message.

With the "Check In Adobe Acrobat Capture PDF with Errors" option, you can allow the check in of a PDF generated by Adobe Acrobat Capture that has any errors in the Adobe Acrobat Capture finished document log. In addition, you can choose to keep the PDF file, so it remains in the release directory where you can review it.

When using Kofax Capture, it is necessary for Kofax Capture to have, at a minimum, index fields that correspond to the content information (metadata) fields that Oracle Content Server requires for content item check in. The following list of index fields must exist in the Kofax document class or the batch class.

Oracle Content Server date fields include both the date and the time in one field. Kofax Capture uses separate fields for date and time. Use the following procedure to concatenate date and time into a single check-in parameter.

If a mapping LIDebug:LIDebug is created, and if the value is set to TRUE during the validation step, the .hda data that is passed from Kofax Capture to Oracle Content Server will be displayed when the release script is run. This allows the user to verify that the correct data and parameters are being passed to the Oracle Content Server.