Release 3.7

Version 3.7 is now available from our repositories.

Encap 3.6 is an internal release and not distributed.

All the improvements from 3.6 is in the 3.7 release.

Encap 3.2 and 3.3 are End of Life

Mobile client SDKs older than version 3.4 will not work. Encap Server 3.7 will only support upgrade from 3.4 and newer.

Google push messaging changes

As of April 10, 2018, Google has deprecated GCM. The GCM server and client APIs are deprecated and will be removed as soon as
April 11, 2019, see: As part of the 3.7 release Encap moves to using the new FCM API for messaging on Android. Clients on earlier Encap versions then 3.7 will loose the ability to use Android push messaging when Google turns of the GCM API.

Support for Java 9,10,11
The Encap Server now requires Java 9,10 or 11 to run.
The recommended version is the newest Java LTS version which is Oracle Java 11

Encap Server now runs on embedded Jetty
We now run the server with embedded Jetty server instead of as a classic .war file.
This means that there is no Jetty distribution packaged with the Encap distribution but instead the whole server is contained in one runnable .jar file.

Which risk data to collect is now configurable
To make it easier to be GDPR complaint, you can now configure what risk parameters you want to store.

Overview of what risk parmeters that is enabled in clients
In both the standard app and the test app there is now an overview of what risk parameters that is enabled and sent back to the server.

REST API for create and read certificates
Certificates can now be manipulated with a REST API.

REST API for changing the application config upgrade improvements
Most parts of the application configuration can now be updated, created or deleted via its REST API interface.

Export logs and metrics for Encap in SaaS mode
Now using ECIES with AES in CBC mode and SHA256 digest.

Outbound proxy support
The server now have support for standard metrics tools made available though the StatsD protocol.