When a user logs onto Access Gateway Advanced Edition using Internet Explorer 7, and then a network interruption occurs, users log on again using their credentials. After this, when users log off, the Web logon portal page does not close as expected.[From AG_455][#23949]If the client computer is running Windows Vista and Internet Explorer 7, the ActiveX control that performs the pre-authentication check and starts Secure Access Client from the portal page does not run unless the Access Gateway's fully-qualified domain name (FQDN) is in the trusted sites list in Internet Explorer. If Internet Explorer 7 is running in protected mode, the Secure Access Client has limited functionality. For example, when installing the Secure Access Client, users are asked to save the executable instead of the installation starting automatically.
To use single sign-on with Vista and Internet Explorer 7, Internet Explorer must be configured for administrator use.[From AG_455][#24021]
When Symantec Enterprise Vault 6.1 is installed in the internal network and the user logs on through the Access Gateway to the Access Interface on the server running Access Gateway Advanced Edition, Outlook Web Access in Internet Explorer fails to respond for approximately five minutes and then starts to work correctly.If users are connecting directly to the server running Access Gateway Advanced Edition, there is no delay.
[From AG_455][#24077, #24092]
There is a 244 character limit for DNS suffixes that are configured on the Name Service Providers tab. The limit is increased to 1023 characters.[From AG_455][#24213]
If the Access Gateway user configuration requires a client certificate for authentication, when users log on, the user name contains the realm name, such as realmname\username. Client certificate criteria can be configured to require only the user name or the realm name. For example, if the expression client_cert_end_user_subject_common_name=user_only is used, the user logging on is authorized for the group only if the common name of the client certificate subject is the user name. If the expression client_cert_end_user_subject_organizational_unit=realm is used, the user logging on is authorized for the group only if the Organizational Unit (OU) of the client certificate subject is the realm name. [From AG_455][#24219]
If the Access Gateway is configured to use the Advanced Access Control option, if an incorrect DNS server is configured on the Access Gateway, it can take a long time for the appliance to restart.[From AG_455][#24225]
If users have McAfee Host Intrusion Prevention installed, the Secure Access Client fails when users attempt to open an application on their local device. When this occurs, the Secure Access Client icon is removed from notification area, however users can connect to resources in the internal network. [From AG_455][#24228]
The Secure Access Client sends connection requests to the local DNS server and not to a configured proxy server to resolve the public name of the Access Gateway. [From AG_455][#24260]
This fix addresses a security vulnerability. For more information, see Knowledge Center article CTX113817.[From AG_455][#24323, #24324, #24325, #24326, #24327]
This fix addresses a security vulnerability. For more information, see Knowledge Center article CTX113816.[From AG_455][#24329, #24330, #24331, #24332, #24333, #24334]
If you have added users to groups on the Access Gateway for which client certificate criteria is configured, and added the same users to other groups that do not require client certificate criteria, users only get the group or groups for which no client certificate criteria is defined. Users do not get the group or groups for which client certificate criteria is defined. [From AG_455][#24341]
When the Secure Access Client is installed, and non-administrative users log on to Windows XP, name resolution fails until the DNS cache is flushed or the connection times out. [From AG_455][#24358]
When users are logged on to the Access Gateway, and the system administrator starts the Citrix Real-time Monitor, the Access Gateway can fail. [From AG_455][#24382]
To enable file logging of client connections, right-click the Secure Access Client icon and click Connection Log. On the Options menu, click Log to file. When this option is enabled, the items that appear in the Connection Log are written to the log file. The log file is overwritten each time the Secure Access Client starts.[From AG_455][#24398]
If client devices are using Windows Vista and are connecting to Version 4.5.5, the Secure Access Client is downloaded from the portal page. If client devices are connecting to earlier versions of the Access Gateway, they must use the standalone version of the Secure Access Client for installation. This version of the Secure Access Client for Vista can be downloaded from the Citrix support Web site. [From AG_455][#24427]
