Remote execution using a global identity

A system comprising:

• one or more processors of a machine;
• and
• at least one memory storing instructions that, when executed by the one or more processors, cause the machine to perform operations 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.

A non-transitory computer readable storage media storing instructions that, when executed by one or more processors, cause the one or more processors to:

• 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.