Abstract: Embodiments described include systems and methods for slogan based sharing of network application objects. The method may include executing a network application on behalf of a client application executed by a first client device. The client application may include an embedded browser. The method may include receiving from the client application a selection of an object of the network application to be shared with a second client device. The method may include selecting a unique sequence of words from a pre-defined list of words, associating the unique sequence of words with the selected object of the network application, transmitting the unique sequence of words to the first client device, and receiving the unique sequence of words from the second client device. The method may include, responsive to receipt of the unique sequence of words from the second client device, accessing the selected object of the network application.

Abstract: Systems and methods for latency masking via prefix caching, by providing a recorded output of launch of a network application to a client device from a point closer to client device, or with lower latency than output of the actual network application can be provided to the client device. The resulting user experience is that of instant or near-instant launch of the application, avoiding network delays communicating with the application server or processing delays from instantiation of virtual machines or other resources to provide the network application.

Abstract: In some aspects, a method for revoking access to a network application on a client device. The method includes establishing, by a client application on a client device responsive to authenticating a user, access to one or more network applications of one or more first servers of a first entity via an embedded browser of the client application, receiving, by the client application, a notification from a second server of a second entity that access for the user to a network application of the one or more network applications is to be revoked, and performing, by the client application responsive to the notification, one or more revoking actions based at least on a policy.

Abstract: Embodiments described include systems and methods of an encrypted cache. An embedded browser of a client application executing on a client device may provide access to a network application accessed via the client application. The embedded browser may detect an event at the client device that causes the network application to send or request application data. The embedded browser may access a copy of the application data from encrypted cache of the embedded browser. The encrypted cache may be maintained for the user and store application data for network application(s) accessed by the user. The embedded browser may use the cached application data for establishing or updating a user interface of the network application for display at the client device.

Abstract: Embodiments described include a method for implementing a privacy policy by a device intermediary to a plurality of clients and one or more servers. The method can include identifying, by a device intermediary to a plurality of clients and one or more servers, network traffic of a user that has not selected an option of a plurality of options of a privacy policy managed by the device. The method can include receiving, by the device, an indicator of a selection by the user of the option from the plurality of options of the privacy policy. The method can include handling, by the device, network traffic of the user according to the selected option of the privacy policy.

Abstract: Embodiments described include systems and methods for presenting additional content for a network application accessed via an embedded browser of a client application are provided. Additional content related to network applications may be presented on client devices. Specifically, activity such as embedded browser activity may be monitored. Responsive to detecting an event based on the monitored activity, additional content related to the network application may be provided. In various embodiments, the additional content is provided to a client application on the client device for presentation on the client device.

Abstract: Embodiments described include systems and methods for receiving push notifications for Software-as-a-Service (SaaS) applications. Push notifications may be received by an agent or notification listener provided by a client application of a client device. The listener may receive and display notifications for a large plurality of SaaS applications, regardless of whether the SaaS applications are currently active in a browser of the client device. The listener agent may be lightweight, consuming very little memory or processor resources, while being able to handle very large numbers of notifications. This may free up resources on the client device, consume less battery for mobile devices, and provide notification functionality for SaaS applications using native notification techniques without requiring the SaaS application developers to rewrite notification systems or switch to an operating system-provided notification system.

Abstract: Embodiments described include systems and methods for reusing content across a plurality of network applications. A client application establishes sessions with the network applications via an embedded browser. The client application identifies a plurality of content provided as input to each of the network applications and stores the plurality of content to storage. The client application determines a point in a first user interface of a first network application in which input from content of the plurality of content is available as input. The embedded browser provides a second user interface from which to select at least a first content of the plurality of content stored in storage from a second network application as input to the first user interface of the first network application. The embedded browser receives, as input to the first user interface, the selection via the second user interface of the first content.

Abstract: Embodiments described include systems and methods for management and pre-establishment of network application and secure communication sessions. Session logs may be analyzed to identify an application or secure communication sessions likely to be accessed, and prior to receiving a request to establish the session, an intermediary (e.g. another device such as an intermediary appliance or other device, or an intermediary agent on a client such as a client application) may pre-establish the session, performing any necessary handshaking or credential or key exchange processes. When the session is subsequently requested (e.g. in response to a user request), the system may immediately begin using the pre-established session. This pre-establishment may be coordinated within the enterprise providing load balancing and scheduling of session establishment to prevent large processing loads at any one point in time.

Abstract: Systems and methods discussed for redirection of launch requests for local applications to corresponding remote applications, such as SaaS or network applications provided by an application server, and access of the corresponding remote application via an embedded browser of a client application. A client application executed by a client device may detect a request of a user to launch a local application of the client device. The client application may determine that the local application corresponds to a network application provided by an application server. The client application may intercept the request to launch the local application, responsive to the determination. An embedded browser of the client application may access the network application from the application server, responsive to interception of the request.

Abstract: Embodiments described include systems and methods for encoding and decoding data for a network application. A client application may include an embedded browser. The embedded browser may establish a session with a network application. The client application may identify a policy specifying a type of data to encode upon input. The embedded browser may detect the type of data of an input field of the network application being displayed in the embedded browser. The embedded browser may, responsive to the detection and the policy, encode the data inputted into the input field or decode encoded data displayed in the input field.

Abstract: Embodiments described include a method for implementing a privacy policy by a device intermediary to a plurality of clients and one or more servers. The method can include identifying, by a device intermediary to a plurality of clients and one or more servers, network traffic of a user that has not selected an option of a plurality of options of a privacy policy managed by the device. The method can include receiving, by the device, an indicator of a selection by the user of the option from the plurality of options of the privacy policy. The method can include handling, by the device, network traffic of the user according to the selected option of the privacy policy.

Abstract: Embodiments described include systems and methods for presenting additional content for a network application accessed via an embedded browser of a client application are provided. Additional content related to network applications may be presented on client devices. Specifically, activity such as embedded browser activity may be monitored. Responsive to detecting an event based on the monitored activity, additional content related to the network application may be provided. In various embodiments, the additional content is provided to a client application on the client device for presentation on the client device.

Abstract: Embodiments described include a method for providing context-aware input across network applications. The method can include establishing a plurality of sessions for a user with a plurality of network applications via an embedded browser within a client application. The method can include storing input activities of the user across the plurality of network applications to a data storage. The method can include detecting input focus on an input element of a network application of the plurality of network applications, the input element having a type of data to be inputted. The method can include identifying one or more inputs of the type of data used in another network application of the plurality of network applications stored in the data storage. The method can include providing the one or more inputs from another network application as selectable input for the input element of the network application.

Abstract: The present disclosure is directed generally to systems and methods for providing load balancing as a service. A load balancer executing on a device intermediary to a server and a plurality of clients can receive a request from an agent executing on the server. The request can be to initiate establishment of a transport layer connection. The load balancer can accept the request to establish the transport layer connection with the server. The load balancer can receive a request to access the server from a client of the plurality of clients. The load balancer can forward the request to the server via the transport layer connection established between the load balancer and the server responsive to the request of the server.

Abstract: Embodiments described include systems and methods for generating and displaying live objects for network applications. Live objects may be created from applications (apps) that are served from and/or hosted on one or more servers, such as web applications and software-as-a-service (SaaS) applications, and shared with one or more recipients. The objects may be loaded or accessed as if they were normal network applications, and the recipients may see the latest or “live” version of content as shown to the live object creator, including user- or device-specific data of the creator, under full access policy control, without requiring access to credentials of the live object creator.

Abstract: Embodiments described include systems and methods for receiving push notifications for Software-as-a-Service (SaaS) applications. Push notifications may be received by an agent or notification listener provided by a client application of a client device. The listener may receive and display notifications for a large plurality of SaaS applications, regardless of whether the SaaS applications are currently active in a browser of the client device. The listener agent may be lightweight, consuming very little memory or processor resources, while being able to handle very large numbers of notifications. This may free up resources on the client device, consume less battery for mobile devices, and provide notification functionality for SaaS applications using native notification techniques without requiring the SaaS application developers to rewrite notification systems or switch to an operating system-provided notification system.

Abstract: In some aspects, a method for revoking access to a network application on a client device. The method includes establishing, by a client application on a client device responsive to authenticating a user, access to one or more network applications of one or more first servers of a first entity via an embedded browser of the client application, receiving, by the client application, a notification from a second server of a second entity that access for the user to a network application of the one or more network applications is to be revoked, and performing, by the client application responsive to the notification, one or more revoking actions based at least on a policy.

Abstract: In some aspects, a method for mediation of a screenshot capture by a client application based on policy includes identifying, by a client application on a client device, a policy for mediating one or more screenshots of content displayed via the client application. An embedded browser within the client application accesses a network application of one or more servers. The method further includes intercepting, by the client application, a request to capture a screenshot of at least a portion of the network application being displayed, determining, by the client application, one or more mediation actions to perform on the screenshot responsive to the policy, performing, by the client application, the one or more mediation actions on the screenshot, and providing, by the client responsive to the request, the screenshot resulting from the one or more mediation actions.

Abstract: Embodiments described include systems and methods for executing in an embedded browser an application script for network applications of different origins. A client application can establish a first session with a first network application of a first entity at a first origin via an embedded browser within the client application and a second session with a second network application of a second entity at a second origin via the embedded browser within the client application. A scripting engine within the client application of a client device of a user at a third origin can identify an application script having instructions to interact with the first network application and the second network application, and can execute the instructions to perform a task across the first network application of the first entity at the first origin and the second network application of the second entity at the second origin.