GAS 4.00 new features

A summary of new features and changes in functionality introduced with Genero Application Server (GAS) 4.00.

Important:

This version of GAS is desupported, use a more recent version of the product.

Important:

This page covers only those new features introduced with the Genero Application Server (GAS) version specified in the page title. Check prior new features pages if you migrate from an earlier version. Make sure to also read the upgrade guide corresponding to this version.

Corresponding upgrade guide: GAS 4.00 upgrade guide.

Previous new features guide: GAS 3.20 new features.

Table 1. Engine and Architecture
Overview Reference
One license consumed per browser:

All applications started from the same browser count as one for licensing purposes, and therefore only one license is used.

 See Genero front-ends and license counting
The EXECUTION element has an optional attribute, CloseAllOnMainExit. This allows you to specify that all child applications are closed gracefully when the user exits the main application. See EXECUTION (for application)
Dispatchers create a pid file. You can set the httpdispatch and fastcgidispatch dispatchers to write their process-id to a file on disk with the --pid-file option of the command. See
The DATA_DIRECTORY element is added to MONITOR to allow you to configure a directory where web services monitoring data is stored. See
The ALERT_SCRIPT element is added to MONITOR to allow you to execute a script when alarms for web services are raised. See ALERT_SCRIPT
HTTP headers specific to an application or service can be defined using HTTP and HEADER elements in the application or service configuration. See:
The RESOURCE res.path.session is defined for the session variable. It points to $(res.appdata.path)/session. See SESSION_DIRECTORY
The $(res.dir.separator) is a resource you can use to specify directory paths for all platforms. It resolves to either a forward slash "/" on a UNIX™-like system including macOS™ or a backward slash "\" on a Windows® system. No additional reference.
Table 2. Web Services and the GAS
Overview Reference
Web service monitoring. This feature allows you to monitor the performance of your services, set alarms, and analyze data. See Monitoring web services
There are improvements to web server integration. The GAS supports HTTP/2. HTTP/2 is the default protocol when installing a web server configured for HTTPS. See:
There are improvements for the management of reverse proxy server, load balancer, and integrated cloud solutions. The GAS supports use of X-Forwarded headers (protocol, host, and port). See:
The ROOT_URL_PREFIX element is deprecated in favor of use of X-Forwarded headers. No additional reference
URL management in REST web service apps is improved. The GAS has enhancements to better detect the URL part after the group/xcf. No additional reference
GIP authentication and access service security cookie updated with SameSite="Strict". See SameSite attribute is now recommended when setting HTTP cookies
The gasadmin monitoring update command is enhanced to enable web service monitoring for services that are not yet available. The GAS displays a message that the configuration is saved and will load once the service is available. See
The gasadmin monitoring preload command allows you to run a list of commands to configure monitoring and alarms from a command file. There are options to overwrite existing configurations and to interact with the configuration at runtime. See
The gasadmin monitoring clean command allows you to remove monitoring data stored in monitoring data (.dat) files. See
Table 3. Single Sign-On (SSO) and delegation
Overview Reference
The OpenIdConnect SSO service provider has options for managing the client IP address sent by the web server (Remote-Addr or X-Forwarded-for) that can apply when reverse proxies, load balancer, or cloud solutions are used. See the Configure management of client remote IP address page in Single Sign-On User Guide
Use the oidc.oauth.request.format configuration entry to define the protocol format to use during OAuth code to ID token exchange. See Set exchange format for OAuth ID token page in Single Sign-On User Guide
The --keys option of ImportOAuth tells the OpenIDConnectService provider where to fetch the OAuth public keys, to validate the ID tokens before granting access to a Genero Application. See The ImportOAuth program page in Single Sign-On User Guide.
By default, the OpenID Connect service performs the exchange of tokens for OAuth authentication in url-encoded format but you can configure this for JSON. See Set exchange format for OAuth ID token page in Single Sign-On User Guide
Table 4. Genero Identity Provider (GIP)
Overview Reference
The GIP supports any database engine supported by Genero. See Genero Identity Platform StarterApp reference page in Single Sign-On User Guide
The StarterApp migrates your existing IDP database to version 4.00, and gives you the option to move from SQLite to the Genero-supported database engine of your choice. See Migrate your Genero Identity Provider database page in Single Sign-On User Guide
Custom properties can be set for a user; these are known as user properties. These properties can be used to provide user-specific details (such as additional passwords) to the operating system or database engine. See Manage custom user properties page in Single Sign-On User Guide
Note:

The new features listed in this topic are available in the latest version of the GAS. Contact your support channel for more details.