US 11,706,218 B2
Systems and methods for controlling sign-on to web applications
Vladimir Mitevski, Rockville, MD (US)
Assigned to NASDAQ, INC., New York, NY (US)
Filed by Nasdaq, Inc., New York, NY (US)
Filed on Dec. 29, 2020, as Appl. No. 17/136,097.
Application 17/136,097 is a continuation of application No. 16/526,490, filed on Jul. 30, 2019, granted, now 10,887,313.
Application 16/526,490 is a continuation of application No. 15/973,771, filed on May 8, 2018, granted, now 10,412,091, issued on Sep. 10, 2019.
Application 15/973,771 is a continuation of application No. 15/342,923, filed on Nov. 3, 2016, granted, now 9,985,972, issued on May 29, 2018.
Claims priority of provisional application 62/252,295, filed on Nov. 6, 2015.
Prior Publication US 2021/0119999 A1, Apr. 22, 2021
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 29/06 (2006.01); H04L 9/40 (2022.01); H04L 67/146 (2022.01); H04L 67/01 (2022.01); H04L 67/02 (2022.01); H04L 67/141 (2022.01); H04L 67/143 (2022.01)
CPC H04L 63/10 (2013.01) [H04L 63/0815 (2013.01); H04L 67/01 (2022.05); H04L 67/02 (2013.01); H04L 67/141 (2013.01); H04L 67/143 (2013.01); H04L 67/146 (2013.01)] 13 Claims
OG exemplary drawing
 
1. A system comprising at least one client device, and at least one server device executing a server-side portion of a web application,
the at least one client device including a first processing system having at least one hardware processor, the first processing system being configured to execute a first client application providing a first client-side portion of the web application and a second client application providing a second client-side portion of the web application, wherein the first client application is a browser,
the at least one server including a second processing system having at least one hardware processor, the second processing system being configured to execute the server-side portion of the web application and to perform operations comprising:
in response to a first access request received from the first client application, causing the first client application to perform a sign-on process and generating a first session, wherein the first client application is subsequently provided access to application data using the first session, and wherein the application data is provided by the server-side portion of the web application;
when a second request is received from the second client application, determining, using at least one characteristic of the second request, whether the first session is useable by the second client application to access said application data, wherein the at least one characteristic includes an identifier included in the second request, and wherein the determining includes determining whether a value corresponding to the identifier is stored in a memory of the at least one server device in association with at least one of a plurality of session records;
in the event that it is determined that the first session is useable by the second client application to access said application data, providing the second client application with access to the application data using the first session;
in the event that it is determined that the first session is not useable by the second client application to access said application data, causing the second client application to perform a sign-on process and generating a second session, wherein the second client application is provided access to the application data using the second session;
generating, in relation to a sign-on by an instance of either the first client application or the second client application executing on another client device, a third session, wherein said instance is subsequently provided access to said application data using the second session; and
in response to generating the third session, deactivating the first session.