3.0400.7 - IT Requirements

This version addresses Licence and Session handling to:

      Authenticate users

      Match users with their data

      Select a general access level

      Maintain sessions across multiple applications and multiple devices

This is made possible by generating, validating and providing applications with a "Security Token", which describes a user, their access level and duration for use of an application. The licence level (access level) and the duration of a licence lease is a part of the "Security Token" description. The framework we employ for creating and maintaining "Security Tokens" is OAuth.

Other changes are:

      Client Sessions exited from the Web Browser without first logging out:

      Will now terminate after one hour

      Can no longer result in a "Duplicate" session

      The ‘Last Use’ date in the ‘Current Users’ Form has been removed because of incorrect data from IIS. This will be reinstated in a Web App in the future

      Sessions from the Mobile App are visible in the ‘Current Users’ Form but cannot be logged out

Some of the steps in this guide may have been performed for previous upgrades. They are included for completeness.

      A TLS certificate installed on the web server, used by Conquest III version 3.0400 and later

      The web server to have the Microsoft .NET Framework version 4.7.2 or later, installed on it

      The Conquest Management Console version 1.0.18 or later. Note: as of version 1.0.18, it is a 64 bit App

      The Conquest database, upgraded to version 3.5 with a SQL script from the Management Console, Management Console Products

      Refresh System Objects must be applied to all of your version 3.5 databases, from the Management Console

If you are updating from version 3.0333.10 or earlier, please read the release notes for versions 3.0400.0 and later:

      3.0400.0 - IT Requirements

      3.0400.2 IT Requirements