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.

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 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: Embodiments described include systems and methods for providing peer-to-peer caching among client applications. A cache coordinator is configured to receive a first request to register an object stored in a cache by a first client application including a first embedded browser. The first embedded browser obtains the object via a session established by the first embedded browser with a first network application on a server of a second entity. The cache coordinator is configured to store a location of the first client application and a hash of the object. The cache coordinator is configured to receive a second request from a second client application. The second request requests the location of the object among peer client applications. The cache coordinator is configured to communicate identification of the location of the first client application to the second client application for retrieving the object from the cache of the first client application.

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: Systems and methods for reporting performance issues or grievances of network applications on client devices are provided. A first server of a first entity receives, from a client application on a client device, a data package including embedded browser activity of an embedded browser of the client application captured responsive to a capture trigger detected by the client application. The embedded browser activity relates to a network application of a second server of a second entity. The first server identifies, based on the embedded browser activity included in the data package, the network application to which the embedded browser activity corresponds. The first server generates, responsive to a report generation trigger corresponding to the network application, an error report based on the data package. The error report is then transmitted via a connection established between the first server and the one or more second servers corresponding to the network application.

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.

Abstract: Described embodiments provide systems and methods for displaying a service graph of microservices based at least on a namespace. A device assigns each of a plurality of microservices of one or more services to a ring of criticality of a plurality of rings of criticality. Each ring of criticality may identify a level of importance of a microservice to the one or more services. The device receives a request to display a service graph of the plurality of microservices according to a selected ring of criticality of the plurality of rings of criticality. The device generates the service graph comprising one or more of the microservices within the selected ring of criticality. The device displays the service graph identifying the one or more microservices within the selected ring of criticality.

Abstract: Described embodiments provide systems and methods for displaying a service graph in association with a time of a detected anomaly. A device may store a plurality of snapshots of a service graph of a plurality of microservices. Each of the snapshots of the service graphs include metrics at a respective time increment from execution of each of the plurality of microservices. The device may detect an anomaly with operation of one or more microservices of the plurality of services. The device may identify a set of snapshots of the service graph within a predetermined time period of a time of the anomaly. The device may display each of the snapshots in the set of snapshots of in sequence corresponding to time increments within the predetermined time period of the time of the anomaly.

Abstract: Described embodiments provide systems and methods for monitoring service level compliance of an entity's use of application programming interfaces of a service. A device can identify a service level definition for a service used by an entity. The service can include a plurality of application programming interfaces (APIs). The service level definition can include one or more thresholds regarding use by the entity of the plurality of APIs. The device can receive, from one or more devices of the entity, a plurality of requests to access one or more APIs of the plurality of APIs of the service. The device can record information about the entity's use of the plurality of APIs of the service. The device can compare the recorded information to the one or more thresholds of the service level definition.

Abstract: Described herein are systems and methods for providing peer-to-peer caching among client applications. A cache coordinator may receive a first request to register an object stored in a cache by a first client application including a first embedded browser. The first embedded browser obtains the object via a session established by the first embedded browser with a first network application on a server of a second entity. The cache coordinator may store a location of the first client application and a hash of the object. The cache coordinator may a second request from a second client application. The second request requests the location of the object among peer client applications. The cache coordinator may communicate identification of the location of the first client application to the second client application for retrieving the object from the cache of the first client application.

Abstract: The present disclosure is directed towards systems and methods for managing application delivery in a network. A device intermediary to a client and one or more servers that provide a plurality of applications, receives a request from the client to access a first application of the plurality of applications. The device holds the request and retrieves, while holding the request, configuration information for an instance of the first application from a configuration repository. The device configures a virtual internet protocol (“VIP”) server using the configuration information for the instance of the first application. The device processes the request via the VIP server.

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: Embodiments described include systems and methods for integrating use of a cloud discovery service into a client application for a network application is provided. A client application can establish, for a user, one or more sessions with one or more network applications via an embedded browser within the client application. A request to access a uniform resource locator (URL) from a network application accessed via the embedded browser can be intercepted. The client application can communicate with a cloud discovery service to determine a location for which to send the URL for the user. The cloud service can select the location from a plurality of locations based at least on a context of the user. The client application can receive, from the cloud discovery service, the location for the URL and, responsive to the request, transmit the URL to the location selected by the cloud discovery service.

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: Systems and methods for enhancing user engagement with network applications include client application executed by a client device, the client application comprising an embedded browser, in communication with one or more application servers providing a plurality of network applications. The embedded browser is configured to access a first network application and a second network application. The client application is configured to: track interactions of a user via the embedded browser with the first network application and the second network application, each interaction having a corresponding score; generate an aggregate score for the user from the scores of each tracked interaction; transmit, to a first application server, the aggregate score for the user; and receive, from the first application server, a score table comprising a plurality of scores of users including the aggregate score for the user. The embedded browser is further configured to display the score table to the user.