US 12,120,189 B2
Remote execution using a global identity
Khalid Zaman Bijon, Santa Cruz, CA (US); Damien Carru, New York, NY (US); Christopher Peter Child, Tiburon, CA (US); Eric Karlson, Alameda, CA (US); and Zheng Mi, Palo Alto, CA (US)
Assigned to Snowflake Inc., Bozeman, MT (US)
Filed by Snowflake Inc., Bozeman, MT (US)
Filed on Oct. 30, 2023, as Appl. No. 18/497,720.
Application 18/497,720 is a continuation of application No. 18/149,799, filed on Jan. 4, 2023, granted, now 11,838,373.
Application 18/149,799 is a continuation of application No. 17/661,096, filed on Apr. 28, 2022, granted, now 11,570,259.
Application 17/661,096 is a continuation of application No. 17/345,101, filed on Jun. 11, 2021, granted, now 11,349,952.
Application 17/345,101 is a continuation of application No. 16/931,808, filed on Jul. 17, 2020, granted, now 11,057,491.
Prior Publication US 2024/0064210 A1, Feb. 22, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 67/306 (2022.01); G06F 9/54 (2006.01); G06F 21/31 (2013.01); H04L 9/40 (2022.01); H04L 41/50 (2022.01); H04L 41/5041 (2022.01); H04L 67/02 (2022.01); H04L 67/10 (2022.01); H04L 67/1097 (2022.01); H04L 67/59 (2022.01); H04L 67/60 (2022.01)
CPC H04L 67/306 (2013.01) [G06F 9/547 (2013.01); G06F 21/31 (2013.01); H04L 41/50 (2013.01); H04L 41/5041 (2013.01); H04L 63/08 (2013.01); H04L 63/0815 (2013.01); H04L 63/102 (2013.01); H04L 63/20 (2013.01); H04L 67/02 (2013.01); H04L 67/10 (2013.01); H04L 67/1097 (2013.01); H04L 67/59 (2022.05); H04L 67/60 (2022.05)] 21 Claims
OG exemplary drawing
 
1. A method comprising:
establishing, at a first deployment, a session pool for a login session for a user providing access to a plurality of accounts associated with an organization based on a global identity;
providing, using the session pool, a first remote session with a first remote session ID using a first proxy user associated with the user for the first remote session;
providing, using the session pool, a second remote session with a second remote session ID using a second proxy user associated with the user for the second remote session;
receiving, in the session pool, a first selection for the first remote session;
transmitting, from the first deployment, a first execution request to a second deployment associated with the first remote session, the second deployment being configured to execute the first execution request in context of the first proxy user;
receiving, in the session pool, a second selection for the second remote session; and
transmitting, from the first deployment, a second execution request to a third deployment associated with the second remote session, the third deployment being configured to execute the second execution request in context of the second proxy user.