Additional notes

This topic contains information about potential issues that you could encounter while using Tungsten OmniPage Capture SDK for Linux 2025.3. Workarounds are provided, as applicable.

1. OmniPage Licensing Agent setup for Page-based licenses

The additional setup defined in this section is required only if you are using Page-based licenses. It ensures that the licensing agent runs correctly and that digital signatures can be validated on modern Linux systems. If you use OEM or Seat licenses, skip this section.

OmniPageLicensing Agent (OPLA) uses .NET 6 as a self-contained library, so installing the .NET 6 runtime separately is not required. At the same time, the SHA1 hashing algorithm is disabled by default on newer Linux distributions for security reasons. Since OPLA requires SHA1 for digital signature verification, the default security policy must be updated.

To update the default security policy:

1. Create a new custom crypto policy file and name it:

/etc/crypto-policies/policies/modules/MY_SHA1.pmod

2. Add the following content to the file:

hash = SHA1+ 
sign = ECDSA-SHA1+ RSA-PSS-SHA1+ RSA-SHA1+ 
shal_in_certs = 1

3. Apply the updated crypto policy with the following command:

update-crypto-policies --set DEFAULT:MY_SHA1

To starting the OPLA service:

1. For a quick setup on systems using systemctl, register and start the OPLA service with:

opla service -register
opla service -start

2. Optionally, if your system does not use systemd or systemctl, you can run OPLA in console mode instead:

opla -console

3. Create a user for OPLA license management by running:

opla user -create -username=[username] -password=[password]