Migrating from 1.10.x

Below is the list of required steps to take into consideration when migrating from eSign Server 1.10.x to 1.11.0.

Dropped support for Internet Explorer

To ensure our product is CVE free we had to upgrade our 3rd party frontend libraries to the latest versions. Unfortunately most of latest versions have dropped support for IE browser.
This also means that Edge in IE mode will no longer work.

Enabling legacy IE11 mode

Even though the new eSign Viewer no longer supports IE11 we have kept the old version of eSign Viewer hidden, should you still wish to use it.

Note that the legacy implementation of eSign Viewer is no longer supported and no support or new features will be available in the future.

To enable legacy compatibility for IE11, the following configuration must be set in esign.config:

"server.viewer.ie11" : true (1)
1 Default value is false

This will cause browsers running IE11 to automatically be redirected to the legacy viewer.
For example, a IE11 browser (or Edge in IE mode) accessing /eSignServer/?session=1234-…​ will be redirected to /eSignServer/legacy/?session=1234-…​

CSS Changes

One of the libraries that had to be updated was Bootstrap, responsible for a large set of UI features.
If you have CSS customizations test and review them agains the new eSign version.

Depending on the type of CSS customizations your instance has, this range from no impact to medium impact.

CSS Changes (legacy IE11 mode)

Due to the changes referred above, if you chose to enable the legacy IE11 mode, you must also create a legacy (IE11) CSS file for each brand you have.

The legacy file must follow the syntax: [brand].legacy.css
For example, if you already have a custom CSS called mybrand.css, must be also include a mybrand.legacy.css file.

Legacy CSS files must be placed on the same folder as the existing CSS customization files (esign_home/css/).

These CSS files will only be used by IE11 browsers.

Database Changes

Microsoft SQL Server (MSSQL) Encryption

We have upgraded the database drivers to the latest versions, namely the Microsoft SQL JDBC Driver to 12.4.x.

MSSQL Driver now enables encryption out-of-the-box.
If your database does not use encryption you have to explicitly append the following to your JDBC url:
encrypt=false;
See: MSSQL Driver Release Notes

Database Hibernate File Removed

eSign no longer reads database configurations from hibernate.cfg.xml.
This feature was deprecated in version 1.8.x, and has now been completely removed.

Ensure that your database configurations are specified in esign.config.
See: eSign 1.9 - Upgrade Steps

Database Configurations Simplified

You no longer need to specify the driver and dialect of your database. This no inferred from you JDBC url.

You may remove the following properties from esign.config:

  • database.dialect

  • database.driver (unless you are using a external datasource)

Database Analytics Upgrade

As eSign’s Analytics capabilities evolve so do its requirements for performance and optimisation.

See the extensive explanation of the upgrade/migration steps required for the proper and performant use of eSign’s Analytics, here

Analytics Business Support Information

Improve your business support analytics by leveraging user domains, channels, and document types to gain more granular insights into user behavior and document interactions. Read how here

Other breaking changes

See the complete list of breaking changes (from 1.10.x to 1.11.0), here.