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	When using Oracle as an eperi sEcure database, SID-based connections are no longer supported. Instead, the Oracle database's Service Name should be used, in order to align with Oracle's best practices.
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