StoreFront 1912 LTSR

Configure communication timeout duration and retry attempts

By default, requests from a Citrix Receiver for Web site to the associated store timeout after three minutes. The store is considered unavailable after one unsuccessful communication attempt. Use the Session Settings task to change the default settings.


In multiple server deployments, use only one server at a time to make changes to the configuration of the server group. Ensure that the Citrix StoreFront management console is not running on any of the other servers in the deployment. Once complete, propagate your configuration changes to the server group so that the other servers in the deployment are updated.

  1. On the Windows Start screen or Apps screen, locate and click the Citrix StoreFront tile.
  2. Select the Stores node in the left pane of the Citrix StoreFront management console, select a store in the center pane, and in the Action pane, select Manage Receiver for Web Site, and click Configure.
  3. Select Session Settings, make your changes, and click OK/Apply to save the changes.

Configure the session timeout

If the session timeout is not appropriately configured on StoreFront, the users may see the following timeout message - “Your session has timed out due to inactivity.” You can reset the session timeout value to increase the inactivity timer to suit your users’ usage pattern.

Complete the following steps to configure the session timeout on StoreFront:

Change the session timeout for StoreFront

  1. On StoreFront, navigate to c:\inetpub\wwwroot\Citrix\<StoreWeb>.
  2. Locate the entry: <sessionState timeout="20" /> in the web.config file.
  3. Change the sessionState timeout to the desired value in minutes.

If you configure the session timeout for Citrix Receiver for Web to more than 1 hour, you must also increase the token maximum lifetime appropriately in the Authentication Service.

  1. On the StoreFront Server, navigate to the path of your store’s Authentication Service.

    • If Storefront is installed on its own server, and you create a store <Store> using the Storefront management console, this path is c:\inetpub\wwwroot\Citrix\<Store>Auth.
    • If Storefront and the Delivery Controller are installed on the same server, when you create a Citrix Virtual Apps and Desktops site using Citrix Studio, a default store is created. In this case the path of the store’s Authentication Service is c:\inetpub\wwwroot\Citrix\Authentication.
  2. In the web.config file, locate the Authentication Token Producer service section similar to the following:

        <clear />
        <service id="9c84499f-3781-42d3-b3e0-2a12efebaa8d" displayName="Authentication Token Producer">
            <relyingParties signingId="462fc209-ecad-44a7-aacb-b75a11b6203a"
            defaultLifetime="01:00:00" maxLifetime="01:00:00">
  3. In the entry <defaultLifetime="01:00:00" maxLifetime="01:00:00"> in this section only, change maxLifetime to the desired value.


Citrix Workspace app for Windows and Citrix Workspace app for Linux. After logging out from the current session, you may see Citrix Virtual Apps and Desktops in the background. However, you should enter your credentials again when you click on any app or desktop after the StoreFront session timeout.

If you configure the session timeout for Citrix Receiver for Web to more than 8 hours, you must also increase token life time appropriately in the StoreWeb.

  1. Navigate to the StoreWeb in your file system, default c:\inetpub\wwwroot\Citrix\<Store>Web.
  2. In the web.config file, locate the section similar to the following:

        <authentication tokenLifeTime="08:00:00" locationURL="Authentication/GetAuthMethods">
  3. In the entry <authentication tokenLifeTime="08:00:00" locationURL="Authentication/GetAuthMethods">, change tokenLifeTime to the desired value.

Restart IIS

Run the iisreset command to apply the changes. Running this command logs off the users from Citrix Receiver for Web, and it does not impact their current ICA session.


The completed lifetime format is .d.hh:mm:ss[.ff]. The maximum lifetime is not limited to 24 hours.

Additional resources

Configure communication timeout duration and retry attempts