Methods and apparatus to manage cloud provider sessions

Abstract

Methods, apparatus, systems and articles of manufacture are disclosed to manage cloud provider sessions. An example apparatus includes at least one non-transitory computer readable medium to store machine readable instructions and processor circuitry of a first device to execute the machine readable instructions to cause the processor circuitry based on a request to perform an action having a duration that is unspecified or sufficiently long, obtain a handle for a user token corresponding to a user that requested the action. Additionally, the processor circuitry is to, during performance of the action by a cloud provider, access the user token using the handle when the cloud provider requires user authorization, the user token to be accessed from a second device.

What is claimed is: 
     
         1 . An apparatus to manage at least one cloud provider session, the apparatus comprising:
 at least one non-transitory computer readable medium to store machine readable instructions; and   processor circuitry of a first device to execute the machine readable instructions to cause the processor circuitry;
 based on a request to perform an action having a duration that is unspecified or sufficiently long, obtain a handle for a user token corresponding to a user that requested the action; and 
 during performance of the action by a cloud provider, access the user token using the handle when the cloud provider requires user authorization, the user token to be accessed from a second device. 
   
     
     
         2 . The apparatus of  claim 1 , wherein the processor circuitry is to, after completion of performance of the action, cause transmission of an acknowledgement to the second device, the acknowledgement to indicate that the second device may at least delete the handle for the user token. 
     
     
         3 . The apparatus of  claim 1 , wherein the handle includes at least one of a universally unique identifier, a globally unique identifier, or a hashed version of at least one credential of the user. 
     
     
         4 . The apparatus of  claim 1 , wherein to obtain the handle for the user token, the processor circuitry is to:
 cause transmission of the user token to the second device; and   obtain the handle, the handle to be sent to the first device by the second device.   
     
     
         5 . The apparatus of  claim 1 , wherein the processor circuitry is to determine the duration of the action based on a characteristic associated with the action. 
     
     
         6 . The apparatus of  claim 5 , wherein the characteristic associated with the action includes at least one of:
 a user input requirement associated with the action;   an amount of data to be transferred during performance of the action;   an interaction with a third-party service to be made during performance of the action;   first historical data associated with the action, the first historical data indicating whether at least one user token expired during a previous performance of the action;   second historical data associated with the action, the second historical data indicating whether the previous performance of the action failed; or   a lifespan field included in the request to perform the action.   
     
     
         7 . The apparatus of  claim 1 , wherein the processor circuitry is to, based on the request to perform the action:
 establish a session with the cloud provider; and   
       refresh a session token for the session before a lifespan of the session token expires. 
     
     
         8 . A non-transitory computer readable medium comprising instructions which, when executed, cause processor circuitry of a first device to at least:
 based on a request to perform an action having a duration that is unspecified or sufficiently long, obtain a handle for a user token corresponding to a user that requested the action; and   during performance of the action by a cloud provider, access the user token using the handle when the cloud provider requires user authorization, the user token to be accessed from a second device.   
     
     
         9 . The non-transitory computer readable medium of  claim 8 , wherein the instruction cause the processor circuitry to, after completion of performance of the action, cause transmission of an acknowledgement to the second device, the acknowledgement to indicate that the second device may at least delete the handle for the user token. 
     
     
         10 . The non-transitory computer readable medium of  claim 8 , wherein the handle includes at least one of a universally unique identifier, a globally unique identifier, or a hashed version of at least one credential of the user. 
     
     
         11 . The non-transitory computer readable medium of  claim 8 , wherein to obtain the handle for the user token, the instructions cause the processor circuitry to:
 cause transmission of the user token to the second device; and   obtain the handle, the handle to be sent to the first device by the second device.   
     
     
         12 . The non-transitory computer readable medium of  claim 8 , wherein the instructions cause the processor circuitry to determine the duration of the action based on a characteristic associated with the action. 
     
     
         13 . The non-transitory computer readable medium of  claim 12 , wherein the characteristic associated with the action includes at least one of:
 a user input requirement associated with the action;   an amount of data to be transferred during performance of the action;   an interaction with a third-party service to be made during performance of the action;   first historical data associated with the action, the first historical data indicating whether at least one user token expired during a previous performance of the action;   second historical data associated with the action, the second historical data indicating whether the previous performance of the action failed; or   a lifespan field included in the request to perform the action.   
     
     
         14 . The non-transitory computer readable medium of  claim 8 , wherein the instructions cause the processor circuitry to, based on the request to perform the action:
 establish a session with the cloud provider; and   
       refresh a session token for the session before a lifespan of the session token expires. 
     
     
         15 . A method to manage at least one cloud provider session, the method comprising:
 based on a request to perform an action having a duration that is unspecified or sufficiently long, obtaining, by executing an instruction with processor circuitry of a first device, a handle for a user token corresponding to a user that requested the action; and   during performance of the action by a cloud provider, accessing, by executing an instruction with the processor circuitry, the user token using the handle when the cloud provider requires user authorization, the user token to be accessed from a second device.   
     
     
         16 . The method of  claim 15 , further including, after completion of performance of the action, transmitting an acknowledgement to the second device, the acknowledgement to indicate that the second device may at least delete the handle for the user token. 
     
     
         17 . The method of  claim 15 , wherein the handle includes at least one of a universally unique identifier, a globally unique identifier, or a hashed version of at least one credential of the user. 
     
     
         18 . The method of  claim 15 , wherein obtaining the handle for the user token includes:
 transmitting the user token to the second device; and   obtaining the handle, the handle to be sent to the first device by the second device.   
     
     
         19 . The method of  claim 15 , further including determining the duration of the action based on a characteristic associated with the action. 
     
     
         20 . The method of  claim 19 , wherein the characteristic associated with the action includes at least one of:
 a user input requirement associated with the action;   an amount of data to be transferred during performance of the action;   an interaction with a third-party service to be made during performance of the action;   first historical data associated with the action, the first historical data indicating whether at least one user token expired during a previous performance of the action;   second historical data associated with the action, the second historical data indicating whether the previous performance of the action failed; or   a lifespan field included in the request to perform the action.   
     
     
         21 . The method of  claim 15 , further including, based on the request to perform the action:
 establishing a session with the cloud provider; and   refreshing a session token for the session before a lifespan of the session token expires.