Limitations

To avoid undesirable side effects, Studio only lets you deploy or undeploy routes created and modified using Studio.

When a user has a pre-existing fragment cookie during authentication, for example, from a previous, incomplete authentication attempt, the pre-exisiting fragment overwrites the current fragment.

To minimize the impact of this limitation, the FragmentFilter cookie has a new property maxAge to configure the maximum duration for which it can remain valid.

IG requires the following configuration to process files bigger than 2 GB and Server Sent Events:

admin.json property streamingEnabled set to true.

When IG is acting as a reverse proxy, and receives HTTP/2 requests, it does not forward the host information provided in the HTTP/2 pseudo-header :authority: to the protected application.

If the protected application is using the HTTP/1 Host header or HTTP/2 :authority: pseudo-header to route requests, an error occurs.

In JBoss, multiple spaces in unquoted cookie values are reduced to one space. For example:

is changed to

The value of System.currentTimeMillis() cannot currently be used in filters, such as JwtBuilderFilter, for claims such as exp and iat.

When IG is running in the Jetty application container, it cannot proxy WebSocket traffic.

The JWT created by JwtBuilderFilter is not encrypted. Carefully consider the security of your configuration when using this filter.

The PasswordReplayFilter filter uses the AM Post Authentication Plugin com.sun.identity.authentication.spi.JwtReplayPassword. The plugin is triggered for AM authentication chains, but not for AM authentication trees.

Do not use the PasswordReplayFilter with AM authentication trees.

The ClientHandler and ReverseProxyHandler property systemProxy can’t be used with a proxy that requires a username and password. Use the handler’s proxy property instead.

When IG runs on versions of Jetty from 9.3.x to 9.4.8, WebSocket notifications are not received correctly. To work around this issue, comment out the entry -module=websocket in Jetty’s start.ini file.

Studio deploys and undeploys routes through a main router named _router, which is the name of the main router in the default configuration. If you use a custom config.json, make sure that it contains a main router named _router.

IG processes responses from asynchronous HTTP clients by using two thread pools of the same size:

Synchronous operation can cause routes to declare a blocked ClientHandler.

To recover from blocking, restart the route, or, if the route is config.json, restart the server. To prevent blocking, increase the number of worker threads.

The SamlFederationHandler does not support filtering. Do not use a SamlFederationHandler as the handler for a Chain.

More generally, do not use this handler when its use depends on something in the response. The response can be handled independently of IG, and can be null when control returns to IG. For example, do not use this handler in a SequenceHandler where the post-condition depends on the response.

IG scripts are not sandboxed, but instead have access to anything in their environment. You must make sure that the scripts that IG loads are safe.

Shared resources cannot be persisted when IG restarts. They must be shared each time that IG restarts.

When a customized config.json is configured in Studio, Studio cannot deploy routes.

The log file of audit events can be overwritten when the log file is rotated.

When CsvAuditEventHandler is used to log audit events, the log file is overwritten if it is rotated before the file suffix, rotationFileSuffix, changes. By default, rotationFileSuffix is defined as a date in the format _yyyy-MM-dd.

Log files are rotated when one of the following limits is reached: maxFileSize, rotationInterval, or rotationTimes.

Set the log rotation parameters so that the log is not likely to rotate before rotationFileSuffix changes.

When SAML is used with an AM policy agent, class cast exceptions occur.

When the user defined mapping is incorrectly set, missing SAML assertions produce an infinite loop during authentication attempts.

For HTTPS, IG can check server certificates. However, mutual authentication, where IG presents its client certificate, is not supported if the client certificate is not the first certificate in the ClientHandler or ReverseProxyHandler keystore.