Citrix Systems, Inc.

Other

Javier Alejandro Figueroa

Ricardo Fernando Feijoo

Bradley Markus Rowe

Gerald Duane Haagsma

Kenneth Scott Bowden

Joel Pineiro

Katia Lopez

Jose Daniel Inclan Llanes

Methods and systems for handling web requests with latency awareness are described herein. A system may receive a web request from a web client, and determine, based on an exponential moving average of past response times, whether to allow the web request to be sent out to the server. Based on this determination, the system may send the web request to the server. The system may receive a response to the web request and update the exponential moving average based on the response time associated with the received response. The response may be forwarded back to the web client.

Web client with response latency awareness

Methods and systems for authentication using multiple identity providers are described herein. A first identity provider may receive, e.g., from a second identity provider, an indication of an authentication request. The first identity provider may retrieve, from a storage device, session information associated with the request. The first identity provider may authenticate, using one or more first functions, based on the session information, and based on authentication credentials received from a user, the user. Based on the authentication, the first identity provider may modify the session information. The second identity provider may authenticate, based on the session information and using one or more second functions, the user. The one or more second functions may comprise providing the user a token based on the session information. The session information may be subsequently deleted.

Multiple identity provider authentication system

Aspects described herein may provide methods and systems for loading a second application from a first application while maintaining a consistent user experience. A technique may comprise receiving, by a client application, a first application from web servers. Upon receipt of a request for a second application, the first application may display a first loading display. The client application and/or the first application may then retrieve the second application and, in the process of retrieving the second application, cause the second application to display a similar loading display. When the client application switches from the first application to the second application, the client may display the second loading display. The similarity of the two loading displays may minimize the interruption perceived by the user. The loading displays may comprise indications of loading status, advertisements, interactive elements, or other content for display to the user.

Intercepted loading of web applications

A technique for maintaining user sessions across multiple web applications includes receiving, by a first web application running on a first server, a cross-application request from a client application. The cross-application request indicates a user action to access a second web application, which runs on a second server. In response to receiving the cross-application request, the first web application sends a single-use password to the client application, which may send the single-use password to the second web application. The first web application receives a session request, which includes the single-use password, from the second web application. In response to receiving the session request, the first web application sends session data to the second web application, enabling the second web application to participate in a session with the client application.

Maintaining a session across multiple web applications

Described embodiments protect clients from open redirect security vulnerabilities in Web applications. A primary application receives a request for an operation to be performed on behalf of a secondary application. The request includes a return location parameter containing i) a return location, and ii) an encrypted portion. After completing the requested operation, the primary application retrieves the return location parameter and a cryptographic key uniquely associated with the secondary application. The primary application decrypts the encrypted portion of the return location parameter to generate a decrypted value, and uses the decrypted value to validate the return location contained in the return location parameter. The primary application transmits a redirect message to the client that causes the client to be redirected to the return location contained in the return location parameter only in response to the return location being successfully validated based on the decrypted value.

Growing community of inventors

Miramar, FL, United States of America

Javier Alejandro Figueroa