Passporting credentials between a mobile app and a web browser

A system comprising:

• a server executing on one or more of a plurality of hardware processors for communication with a client device via a network,
• the server receiving login credentials for a user from the client device for a device session between the server and a native app executing on the client device, and
• the server returning a device session token including credentials authenticating the user for the device session between the server and the native app;
• a database in communication with the server and to which the sever has access;
• a common gateway interface (CGI) executing on one or more of the plurality of hardware processors for communication with the client device via the network,
• the CGI having access to the database,
• the CGI receiving the device session token from an embedded browser executing, on the client device, a web flow session between the embedded browser and the CGI;
• the CGI accessing the database according to the device session token received from the client device and the credentials to retrieve a stored session data, including an authorization object;
• the CGI determining, based on the device session token received from the client device, the credentials, the stored session data, and the authorization object, whether the device session is active or the device session has expired;
• and
• the CGI converting, based on determining the device session is active, the authorization object to a web flow session authorization token to be transmitted to the embedded browser to authenticate the web flow session between the embedded browser and the CGI to continue the device session between the server and the native app with the user already logged in.

A method comprising:

• receiving a device session token by a client device from a server in communication via a network with the client device, the device session token authenticating a device session between the server and a native app executing on the client device, the device session token including credentials authenticating a user for the device session between the server and the native app executing on the client device;
• invoking an embedded web browser, by the native app, to execute on the client device;
• passing by the native app the device session token to the embedded web browser for authentication of a web session that continues the device session with the device session authentication and without requiring additional authentication for the web session between the embedded web browser and a common gateway interface in communication via the network with the client device;
• passing the device session token by the embedded web browser executing on the client device via the network to the common gateway interface;
• receiving from the common gateway interface a web flow authorization token converted from the device session token using the credentials for authenticating the user for the device session between the server and the native app executing on the client device;
• authenticating the web session as a continuation of the device session authenticated by the device session token;
• and
• communicating back from the web session to the native app so that the web flow authorization token and the device session token both share the same underlying device session and the device session remains active while the web session is active.

A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform a operations comprising:

• receiving a device session token by the mobile device from a server in communication via a network with the mobile device, the device session token authenticating a device session between the server and a native app executing on the mobile device, the device session token including credentials authenticating a user for the device session between the server and the native app executing on the mobile device;
• invoking an embedded web browser, by the native app, to execute on the mobile device;
• passing by the native app the device session token to the embedded web browser for authentication of a web session that continues the device session with the device session authentication and without requiring additional authentication for the web session between the embedded web browser and a common gateway interface in communication via the network with the mobile device;
• passing the device session token by the embedded web browser executing on the mobile device via the network to the common gateway interface;
• receiving from the common gateway interface a web flow authorization token converted from the device session token using the credentials for authenticating the user for the device session between the server and the native app executing on the mobile device;
• authenticating the web session as a continuation of the device session authenticated by the device session token;
• and
• communicating back from the web session to the native app so that the web flow authorization token and the device session token both share the same underlying device session and the device session remains active while the web session is active.