The Citrix Gateway service release to cloud release notes describe the new features, enhancements to existing features, fixed issues, and known issues available in a service release. The release notes include one or more of the following sections:
What’s new: The new features and enhancements available in the current release.
Fixed issues: The issues that are fixed in the current release.
Known issues: The issues that exist in the current release and their workarounds, wherever applicable.
V3.5 (August 19, 2019)
- Launching an Enterprise Web app for an NTLM authentication enabled resource from Citrix Workspace fails if both of the following conditions are met:
- Customer’s data center has a proxy server and that proxy server is configured on the Gateway Connector
- Web App is configured with no SSO (Don’t use SSO)
- Publish the Web app as a Basic SSO app or
- Do not have a proxy server configured on Gateway Connector
If there are SSL intercepting devices in the on premises data center where the Citrix Gateway Connector must be deployed, the connector registration does not succeed if SSL interception is enabled for the following FQDNs.
The SSL interception must be disabled for these FQDNs for successful connector registration.
Download logs option is available in Gateway Connector from version 401.251. If you are on an earlier version of connector and you upgrade the connector to version 401.251, you cannot download the logs even though the Download Logs link is available.
- Edits made in the Access Control page are not propagated to the database because the failed jobs were re-tried incorrectly. [NGSWS-7733]
If a customer’s data center has an authentication-enabled proxy server configured for Gateway Connector, the connector fails to register itself with Citrix Cloud. [NGSWS-7231]
When adding an Enterprise Web app, if the FQDN contains an underscore ( _ ) in the domain name, an error is displayed. [NGSWS-7033]
If the SSO type for a SaaS app is changed from Don’t use SSO to SAML, the configuration change fails. [NGSWS-7466]
Kerberos authentication support for Citrix Gateway Connector to outbound proxy [NGSWS-6410]
Kerberos authentication is now supported for the traffic from Citrix Gateway Connector to outbound proxy. Gateway Connector uses the configured proxy credentials to authenticate to the outbound proxy.
In rare cases, web filtering UI configuration changes do not take effect to the tenant traffic. [NGSWS-7147]
Memory leaks on ICA service nodes, resulting in a high memory usage. [NGSWS-7014]
Application fails to launch because Citrix Gateway service node does not send the X-NGS-Session-Id header as part of policy document retrieval request to the CVMs. [NGSWS-6963]
Authentication and app enumeration on Citrix Gateway service fail if the token size for authentication exceeds 64 KB. [NGSWS-5932]
Web/SaaS apps traffic can now be routed via a corporate-network-hosted Gateway-Connector thus avoiding two factor authentication. If a customer has published a SaaS app that is hosted outside the corporate network, support is now added to authenticate traffic for that app to go through an on premises Gateway Connector.
For example, consider that a customer has an Okta protected SaaS app (like Workday). The customer may want that even though the actual Workday data traffic is not routed via Citrix Gateway service, the authentication traffic to Okta server is routed through Citrix Gateway service via an on premises Gateway Connector. This helps a customer to avoid a second factor authentication from Okta server as the user is connecting to Okta server from within the corporate network.
Disabling Filtering Website Lists and Website Categorization. Filtering Website Lists and Website Categorization can be disabled if the admin chooses not to apply these functionalities for a specific customer.
Automatic geo routing for secure browser service redirects. Automatic geo routing is now enabled for secure browser service redirects.
Web app launch fails for a customer when the value of the CustomerId is in camel case.
Connection to a Secure Mail server is not possible with FQDN. If the customer configuration has FQDN configured for the mail server, then the connection fails.
App launch fails after the Gateway Service session times out. The end user needs to re-login to access the apps.
When renaming a SaaS app, the name changes in the GUI but does not change in the Workspace app. Similarly, when changing or adding an icon of certain SaaS apps and Web apps, the icon updates in the GUI but is not propagated to the Workspace app.
If Enhanced Security is enabled on a Web app (hosted inside corporate network) and if that app is launched from a native browser, then the app launch is redirected to secure browser service because native browser cannot enforce enhanced security policies.
An app fails to launch if the app FQDN is in camel case.
Deleted applications still show up in the cloud library.
When there is an outbound proxy configured for Gateway Connector and if the proxy has authentication enabled, Gateway Connector cannot perform authentication with the proxy server.
In race conditions, app configuration does not get propagated intermittently. [NGSWS-4958]
App launch fails intermittently with a “Failed to fetch Policy Document.” error.
Deleted apps still show up in Workspace app.
Gateway Service supports form response sizes up to 32k for Web applications with form based SSO which is not sufficient for certain applications. With this fix, Gateway Service now supports form response sizes of up to 64k for Web Applications with form based SSO type.
“Detect” button is added in the “Add a Gateway Connector” page. The Detect button is used to refresh the list of connectors, allowing the newly added connector to reflect in the Web app connectivity section.
A new category “Malicious and Dangerous” is added in the “Access Control Web Filtering” categories. A new category named Malicious and Dangerous in the Access Control Web Filtering categories is added under the Malware and Spam group.
Sometimes, Gateway Connector crashes when multiple threads access the same resource.
In some cases, delete operation using an administrator credential for a Web or SaaS application that does not have subscribed users or groups fails.
Configurations for Citrix Gateway Connector are lost upon editing Form based SSO parameters.
Add another app option does not work when you access the option navigating as follows, Edit app>Overview>Add another app.
A newly added connector takes too long to show up in the UI.
Outbound connections from a connector fail when the connector uses the external FQDN value for the connection via an outbound proxy.
In some cases, app enumeration fails for a customer when the value of the CC-Customer-Id field has letters in lower case and in upper case.
Upon launching an application in a Secure Browser session, the display message incorrectly shows “Connecting to [application id]” instead of “Connecting to “[application name].”
Athena tokens which exceed 64k bytes in size upon decompressing is not supported.