Enhanced token transfer
Methods and systems for token transfer are described herein. A remote computing device may receive, from a mobile computing device, a public key of a public-private key pair. The public key may be associated with a first application of the mobile computing device. The first application may be configured to send credentials to a second application of the mobile computing device. The second application may be isolated from other applications executable on the mobile computing device. The remote computing device may receive, from the first application, a token. The token may have been previously issued to the first application and may have been encrypted, using the public key, by the first application. The remote computing device may send, to the second application, the token to enable the second application to authenticate with a plurality of services that interact with the second application.
1. A method comprising:
receiving, by a remote computing device and from a mobile computing device, a public key of a public-private key pair, wherein a first application of the mobile computing device is configured to send credentials to a second application of the mobile computing device, wherein the second application is isolated from other applications executable on the mobile computing device, and wherein the public key was generated by the second application based on a characteristic of the mobile computing device;
receiving, from the first application, a token, wherein the token was generated based on authentication, using a single set of credentials, of the first application and was encrypted, using the public key, by the first application; and
sending, to the second application, the token to enable the second application to authenticate, with the single set of credentials, with a plurality of services that interact with the second application.
2. The method of claim 1 , wherein sending the public key comprises:
determining, based on the characteristic of the mobile computing device, that the first application and the second application execute on a same computing device.
3. The method of claim 1 , further comprising:
storing the public key in a database, wherein sending the public key comprises querying, using the characteristic of the mobile computing device, the database to retrieve the public key.
4. The method of claim 1 , wherein receiving the public key comprises:
receiving, from a management application of the mobile computing device, the public key, the management application configured to manage the second application.
5. The method of claim 1 , wherein sending the public key comprises:
sending, to the first application, a Uniform Resource Locator (URL) configured to provide the public key.
6. The method of claim 1 , further comprising:
storing the public key in storage of the remote computing device; and
deleting the public key from storage of the remote computing device after a period of time.
7. The method of claim 1 , further comprising:
storing the public key in storage of the remote computing device; and
deleting, after sending the token, the public key from storage of the remote computing device.
8. The method of claim 1 , wherein the characteristic of the mobile computing device comprises a unique identifier of the mobile computing device.
9. A method comprising:
receiving, by a remote computing device and from a mobile computing device, data associated with a first application of the mobile computing device and a second application of the mobile computing device, wherein the second application is isolated from other applications executable on the mobile computing device;
causing the second application to generate a public-private key pair based on a characteristic of the mobile computing device;
receiving, from the first application, a token, wherein the token was generated based on authentication, using a single set of credentials, of the first application and was encrypted, using a public key of the public-private key pair, by the first application; and
sending, to the second application, the token to enable the second application to authenticate, with the single set of credentials, with a plurality of services that interact with the second application.
10. The method of claim 9 , wherein causing the second application to generate the public-private key pair is based on determining, based on the characteristic of the mobile computing device, that the first application and the second application execute on a same computing device.
11. The method of claim 9 , wherein receiving the public key comprises:
receiving, from a mobile computing device management application configured to manage the second application, the public key.
12. The method of claim 9 , wherein sending the public key to the first application comprises:
sending, to the first application, a Uniform Resource Locator (URL) configured to provide the public key.
13. The method of claim 9 , further comprising:
storing the public key in storage of the remote computing device; and
deleting the public key from storage of the remote computing device after a predetermined time period.
14. The method of claim 9 , further comprising:
storing the public key in storage of the remote computing device; and
deleting, after sending the token, the public key from storage of the remote computing device.
15. The method of claim 9 , wherein the data is configured to cause the second application to generate the public-private key pair.
16. A method comprising:
providing, by a mobile computing device, data to a remote computing device, the data associated with a first application of the mobile computing device and a second application of the mobile computing device, and the second application being isolated from other applications executable on the mobile computing device;
providing, by the mobile computing device, a public key, of a public-private key pair, to the remote computing device, the public-private key pair being generated by the second application and with use of a characteristic of the mobile computing device;
receiving, by the mobile computing device, the public key from the remote computing device, the public key being verifiable by the first application to determine that the public key was generated with use of the characteristic of the mobile computing device;
receiving, by the mobile computing device, a token from the remote computing device, the token being generated based on authentication, using a single set of credentials, of the first application and being encrypted, using the public key, by the first application; and
executing, by the mobile computing device, the second application with use of the received token to enable the second application to authenticate, with the single set of credentials, with a plurality of services that interact with the second application.
17. The method of claim 16 , wherein providing the public key comprises providing the public key using a mobile computing device management application.
18. The method of claim 16 , wherein the characteristic of the mobile computing device comprises a unique identifier of the mobile computing device.
19. The method of claim 16 , wherein executing the second application comprises:
decrypting, using at least a portion of the public-private key pair, the token.
20. The method of claim 16 , wherein the token corresponds to authentication of a user of the mobile computing device based on the single set of credentials.