Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

What's new in 5.1.0

Release date: 2021-07-01

5.0.0 was an internal release, hence, this list includes changes introduced in 5.1.0 as well as 5.0.0.

  • Important updates to system requirements:
    • New Python version and additional Python modules required on the environments needed to set up and run Lequinox platform.
    • 5.1.0 will only support the Android version of Lequinox professional ID.
  • Updates to the platform REST API:
    • Functions for managing external users (individuals from organisations that are not in your organisation), under specific external user agreements.
    • Functions for managing transactions for external users, managed via an application, or the Lequinox platform.
    • Functions for verifying a server account.
    • The multisign service is optional when the platform server account is the creator in a transaction.
  • Updates to the Lequinox console:
    • The possibility to manage external users.
    • A new look and feel.
  • Internal users no longer require personal identities, and hence, collecting and sharing references for personal identities is no longer supported.
  • Performance optimisations.

Compatibility

This release will be compatible with these versions:

  • 4.2.0

We strongly recommend a new 5.1.0 installation.*

Deprecated and removed 

  • From Lequinox platform 5.1.0, Lequinox process engine, and hence Web form application, are no longer supported.
  • From Lequinox platform 5.1.0, the iOS version of Lequinox professional is no longer supported.

* Specific instructions for customers currently on version 4.x.x

To reuse an existing VM with an existing Lequinox platform version 4.x.x: 

  1. Create a VM snapshot (recommended).
  2. Stop WildFly.
  3. Delete the contents of the following directories in WildFly:
    1. tmp
    2. log
    3. deployments.
  4. Delete the contents of the archive_service filestore directory.
  5. Follow the instructions for a new 5.1.0 installation.

When you have performed a fresh installation, we will provide you with a new API key required for activating your new platform.

  • No labels