Citrix cag download. Citrix Secure Access for Windows release notes
Close your browser. Aviso legal.
CAG – Using MacOS - DigitalVA - We’re here anytime, day or night - 24/7
Current Release. How users connect with the Citrix Secure Access agent. Select the user access method. Deploy Citrix Secure Access agent for user access.
Select the Citrix Secure Access agent for users. How users connect with Citrix Workspace app. Decouple the Citrix Workspace app icon. Configure the Citrix Workspace app home page on Citrix Gateway. Apply the Citrix Workspace app theme to the Citrix Gateway logon page. Create a custom theme for the Citrix Gateway logon page. Citrix Gateway VPN client registry keys. Enforce the HttpOnly flag on authentication cookies. Customize the user portal for VPN users.
Prompt users to upgrade older or unsupported browsers by creating a custom page. Configure domain access for users. Enable clientless access persistent cookies. Save user settings for clientless access through Web Interface. Configure the Client Choices page. Configure access scenario fallback. Configure connections for the Citrix Secure Access agent. Configure the number of user sessions.
Configure time-out settings. Connect to internal network resources. Configure split tunneling. Configure client interception. Configure name service resolution. Enable proxy support for user connections. Configure address pools. Support for VoIP phones. Configuring application access for the Citrix Secure Access agent for Java. Configure Access Interface. Configure SmartAccess.
Traffic policies. Session policies. Configure Citrix Gateway session policies for StoreFront. Advanced policy support for Enterprise bookmarks. Endpoint polices. Preauthentication policies and profiles. Post-authentication policies. Preauthentication device check expressions for user devices.
EPA as a factor in nFactor authentication. EPA scan classification types on Windows client. Advanced Endpoint Analysis scans. Manage user sessions. Always On. Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente. It contains networking considerations and the ideal approach for resolving issues from the networking perspective.
When users connect with the Citrix Secure Access agent, Secure Hub, or Citrix Workspace app, the client software establishes a secure tunnel over port or any configured port on Citrix Gateway and sends authentication information. Once the tunnel has been established, Citrix Gateway sends configuration information to the Citrix Secure Access agent, Citrix Secure Hub, or Citrix Workspace app describing the networks to be secured.
That information also contains an IP address if you enable intranet IPs. You configure user device connections by defining the resources users can access in the internal network. Configuring user device connections includes the following:. You configure most user device connections by using a profile that is part of a session policy. You can also define user device connection settings by using per-authentication, traffic, and authorization policies.
They can also be configured using intranet applications. Select the Name Servers node, as shown in the following screenshot. Ensure that the DNS name server is listed. For each component you configure in the Configure Citrix Gateway Session Profile dialog box, ensure that you select the Override Global option for the respective component. When the plug-in starts, a browser instance starts and gets killed automatically. Ensure that the Client Cleanup Prompt option is selected if necessary, as shown in the following screenshot:.
Create a session policy with a required expression or true, as shown in the following screenshot:. Bind the Session policy to the VPN virtual server. For details, see Binding Session Policies. Create an Intranet Application. When planning your Citrix Gateway deployment, it is important to consider split tunneling and the default authorization action and authorization policies.
For example, you have an authorization policy that allows access to a network resource. You have split tunneling set to ON and you do not configure intranet applications to send network traffic through Citrix Gateway. When Citrix Gateway has this type of configuration, access to the resource is allowed, but users cannot access the resource.
If the authorization policy denies access to a network resource, the Citrix Secure Access agent sends traffic to Citrix Gateway, but access to the resource is denied in the following conditions. Configuring Authorization. Configuring Authorization Policies. Setting Default Global Authorization. Complete the parameters for allowing network access, click Create , and then click Close.
This new packet is going to be sourced from the SNIP toward the intranet application. From here, the intranet application gets the packet, processes it and then attempts to reply to the source of that packet the SNIP in this case.
The SNIP gets the packet and sends the reply to the client who made the request. Be advised that the Citrix ADC appliance is going to own the Intranet IP pool and for this reason these ranges must not be used in the internal network. This new packet is going to be sourced from one of the Intranet IPs toward the intranet application. It is recommended to point the traffic back to the SNIP that holds the route from which the packet leaves the Citrix ADC appliance the first time to avoid any asymmetric traffic.
When the split tunnel is set to off, the Citrix Secure Access agent captures all network traffic originating from a user device and sends the traffic through the VPN tunnel to Citrix Gateway. In other words, the VPN client establishes a default route from the client PC pointing to the Citrix Gateway VIP, meaning that all the traffic needs to be sent through the tunnel to get to the destination. Since all the traffic is going to be sent through the tunnel, authorization policies must determine whether the traffic is allowed to pass through to internal network resources or be denied.
If the goal is to monitor and control this web traffic then you must forward these requests to an external Proxy using the Citrix ADC appliance. User devices can connect through a proxy server for access to internal networks as well. To enable proxy support for user connections, you must specify these settings on Citrix Gateway.
You can specify the IP address and port used by the proxy server on Citrix Gateway. The proxy server is used as a forward proxy for all further connections to the internal network. You can enable split tunneling to prevent the Citrix Secure Access agent from sending unnecessary network traffic to Citrix Gateway. If the split tunnel is enabled, the Citrix Secure Access agent sends only traffic destined for networks protected intranet applications by Citrix Gateway through the VPN tunnel.
The Citrix Secure Access agent does not send network traffic destined for unprotected networks to Citrix Gateway. When the Citrix Secure Access agent starts, it obtains the list of intranet applications from Citrix Gateway and establishes a route for each subnet defined on the intranet application tab in the client PC.
The Citrix Secure Access agent examines all packets transmitted from the user device and compares the addresses within the packets to the list of intranet applications routing table created when the VPN connection was started. If the destination address in the packet is within one of the intranet applications, the Citrix Secure Access agent sends the packet through the VPN tunnel to Citrix Gateway. If the destination address is not in a defined intranet application, the packet is not encrypted and the user device then routes the packet appropriately using the default routing originally defined on the client PC.
Citrix Gateway also supports reverse split tunneling, which defines the network traffic that Citrix Gateway does not intercept.
If you set split tunneling to reverse, intranet applications define the network traffic that Citrix Gateway does not intercept. When you enable reverse split tunneling, all network traffic directed to internal IP addresses bypasses the VPN tunnel, while other traffic goes through Citrix Gateway.
