Known limitations

The following items are known limitations in this release.

Affected Components Description
eperi sEcure Platform

If eperi sEcure Platform has been manually deployed on Tomcat, its Java process will continue to run even if Tomcat stops. In such cases, the associated Java process will need to be manually terminated.
eperi sEcure Platform
The following functional limitations are specific to conditional tokenization.
  • Conditional tokenization must be activated via the eperi sEcure Platform Enable conditions on token profiles advanced setting.
  • To deactivate this functionality, all token profiles that are using it must be deactivated before conditional tokenization can be deactivated via its advanced setting.
  • When adding or editing conditions, previously tokenized values remain unchanged, i.e., retokenization is not performed retroactively.
  • Conditional rules cannot reference token profiles that themselves contain further conditional rules (no nesting).
  • Intersecting of conditions is not allowed.
  • Currently, only the following token profiles are supported:
    • de.eperi.ca.email
    • de.eperi.ca.number18
    • pattern Token Profile
    • KFZ
    • SSN
Affected Components Description
eperi sEcure Platform

In case the eperi sEcure Platform has been deployed manually on Tomcat, there is the following limitation: even if Tomcat has been stopped, the respective Java process will continue to run. Therefore it is necessary to kill this process manually.
eperi sEcure Platform

Configuring Ignite for improving eperi sEcure Platform cluster management will be made more convenient in an upcoming release.

Functional limitations

General Limitations
  • Any column assigned the useAsCUrsor method needs to be defined as numeric and unique. Ideally, a table's primary key column is used, provided it is numeric.
  • Any column assigned the useAsCUrsor method cannot be protected and will be inserted unaltered in the destination table.
  • By default, OFFSET pagination is used if no cursor column is specified.
  • By default, all data to be protected will read into memory to increase performance. For tables with very large amounts of data, the Atomic Batch Mode advanced setting can be used to protect the data in batches in order to conserve system resources.
Limitations when using Microsoft SQL Server
  • Schema names are currently not supported. The database's default schema will be used.
  • Named instances are not supported.
  • Destination tables cannot have an IDENTITY INSERT restriction.
Limitations when using Oracle
  • Table names need to be all uppercase.
  • When assigning the User Name for the connection to Oracle, it may be necessary for certain schemas/users to include their role, e.g., SYS AS SYSDBA.
  • A table's primary key column must be included when creating a protection policy. Without the primary key column, no data will be inserted in the destination table.

For details on these limitations and possible workarounds, please contact us.