CURRENT RELEASE

THE LATEST RELEASE:

2.2.0 was published on 31.08.2017

DOCUMENTATION OF THE RELEASE:

Read documentation of 2.2.0 release:

IMPORTANT NOTE ON OPENJDK:

with introduction of latest Jetty HTTP server (used by Unity) it was observed that Firefox browser have troubles connecting to Unity launched on some of the OpenJDK distributions (e.g. Fedora). This is due to disabling EC TLS ciphers in affected OpenJDK. In case of troubles please use Oracle Java RE.

GENERAL INFORMATION ABOUT THE RELEASE:

There are two distribution formats:

  • tar.gz bundle which can be unpacked and this way installed in a single directory,
  • rpm which can be installed system-wide in the Linux standard locations.

The rpm is build and tested on Centos 7, noarch. It should work flawlessly also on SL7 and recent Fedora distributions. We may build packages for other distributions in future, however the tar.gz format should be fully portable. Java 8 JRE is the primary installation prerequisite. For more detailed installation information please check the Unity manual.

2.2.X RELEASE SERIES

Release 2.2.0 brings major improvements in three areas:

  • Organization of default configuration is changed to use so called configuration modules. Configuration modules allow for grouping together logically connected configuration parts which so far needed to be placed in various places. For instance a module can contain configuration of 2 related endpoints with their all authenticators and translation profiles.
    • This feature is based on a very simple general enhancement of the configuration file syntax: it is possible to include external files and to use variables.
  • A new PAM password verificator is available. Also importing users from host OS is possible. With this feature UNIX users who can login to the machine hosting Unity can also login to Unity with the very same credentials.
  • UNICORE integration is now super easy with a new, dedicated configuration modules. For the simplest case (UNICORE quickstart + demo certificates) it is enough to enable the two UNICORE configuration modules and start the server. Other scenarios can be quite easily derived from the one provided. By default UNICORE configuration module is using PAM authentication. What is more a new UNICORE intgration HowTo is provided (see Suppoort).

Upgrade from 1.9.x to 2.0.0 series is not 100% automated, if upgrading from 1.9.x please follow carefully instructions from the 2.0.0 release. Upgrade from 2.1.0 is fully automatic, there were no changes in the storage layer. The old configuration syntax is 100% unchanged.

DETAILED LIST OF CHANGES

Bugs fixed:
  • 617 OAuth scopes must be returned when different from the requested
  • 616 OAuth consent screen cannot be generated with dynamic attributes without type declared in attribute schema
  • 614 Import from 1.9x to 2.x with contents from very old releases fails
  • 613 Log4j configuration is not reloaded at runtime
  • 612 Groovy script test runner fails to start
New features:
  • 619 Prepare UNICORE integraiton howto and config modules
  • 615 Flexible task-focussed configuration
  • 611 PAM and Host OS integration

OLDER REVISIONS

Here you can download previous versions from the series and read their documentation:

There were no older revisions in this series yet.