GAS 4.01 new features

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

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.01 upgrade guide.

Previous new features guide: GAS 4.00 new features.

Table 1. Engine and Architecture
Overview Reference
The gasadmin session command has an --idle-time option. This command allows you to check if a session has user activity. It gives you the number of seconds since the last user activity on all applications in a specified session. See gasadminsession command options.
The GAS has been enhanced to support applications embedded in a third-party portal. This allows you to configure several independent applications in one xcf file that can be executed in the same Genero Browser Client (GBC) and rendered in a single web page. See Configure web applications for third-party portal
The APPLICATION element has an optional attribute, SinglePageApplications. This allows you to specify that applications configured in the APPLICATIONS element of the xcf file are executed as Single Page applications. See APPLICATION (for application) and APPLICATIONS
The gasadmin session command is enhanced with option --whoami to display the kind of dispatcher the GAS is using: httpdispatch, fastcgidispatch, or isapidispatch. See gasadmin session command options.
The gasadmin reset-log command allows you to reconfigure the logging for the running dispatcher, as well as for specific sessions. See gasadmin reset-log command options.
Starting at 4.01.01
The following gasadmin commands are enhanced:
  • The gasadmin session --list-sessions command is enhanced to display fglrun process ids started in the current session by the uaproxy or gwsproxy.
  • The gasadmin --version command now includes the date and time of when the GAS package was built.
 See gasadmin tool.
Starting at 4.01.02
The gasadmin send-message command allows an administrator of the GAS to send messages to connected users on the specified applications and sessions, or to connected user on all sessions running in the GAS. See gasadmin and Send administrative messages to user agents.
The gasadmin close-session and gasadmin close-all-sessions commands allow an administrator of the GAS to close specified applications and sessions, or to close all sessions running in the GAS gracefully. The commands also have options to send a message or an end URL to the user agents on closing the sessions. See gasadmin
On Unix-like platforms you can use systemd to manage the GAS dispatchers. You can perform various management tasks, such as starting and stopping the dispatcher, using systemctl commands. Templates for configuring GAS systemd are provided in FGLASDIR/systemd/
Warning:

The systemd feature is available on Linux® only.

 See Systemd service template
Starting at 4.01.03
On Unix-like and macOS™ platforms you can redirect logs to the system log. Output to the system logs can be configured in the OUTPUT element.
Warning:

The syslog feature can not be enabled on Windows®.

 See OUTPUT (under LOG)
Table 2. Web services and the GAS
Overview Reference
Starting at 4.01.06
There are improvements for the management of reverse proxy server, load balancer, and integrated cloud solutions. The GAS supports use of X-Forwarded header X-Forwarded-Prefix. X-Forwarded-Prefix should contain the PathBase (/path/base) of the URI. See:
Table 3. Single Sign-On (SSO) and delegation
Overview Reference
The oidc.app.start.mode configuration entry of the OpenidConnectServiceProvider service defines how the identity of the client is verified before starting the application. You can configure "gnonce" (genero number once) or a cookie. See Configure application starting mode page in Single Sign-On User Guide
Starting at 4.01.02
The OpenID Connect service of FGLGWS has enhancements to how scopes are exchanged. The Genero Identity Provider (GIP) follows the standard RFC 8693 as the default method when creating OAuth ID and access tokens with the scope parameter. See Support for RFC 8693 in the Genero Identity Provider (GIP) creation of OAuth ID and access tokens with scopes
Starting at 4.01.04
The OpenID Connect service configuration of FGLGWS has a new entry (oidc.accesstoken.decode) added to decode roles and scopes in the access token. See New option oidc.accesstoken.decode for decoding access tokens with roles and scopes
Note:

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