Authentication mechanism
A system and method including: receiving an authorization request originating from an authorization module of an application executing on a client device, where the authorization request includes an identifier identifying the client device; causing transmission, based on the identifier, of a verification message to the client device, where the verification message includes a verification code; receiving a confirmation of the verification code from the authorization module of the application executing on the client device; authenticating the application based on the receiving the confirmation of the verification code; determining that the client device identified by the identifier corresponds to a user account including secure user data associated with a user; and transmitting a unique token verifying that the application is authorized to sign into the user account, where: the unique token uniquely identifies the user account to the application, and the secure user data is not shared with the application.
1. A method for authorizing an application on a client device comprising:
causing, by an authorization module of the application executing on the client device, a transmission of an authorization request, including an identifier of the client device, to an identity system, wherein the authorization request is transmitted for verification that the client device identified by the identifier corresponds to a particular user account;
receiving, at the client device, a verification message generated by the identity system based on the identifier of the client device, the verification message comprising a verification code;
providing the verification code from the received verification message to the authorization module;
causing, by the authorization module, a transmission of a confirmation of the verification code to the identity system to authenticate the application based on receiving the confirmation of the verification code;
receiving a token from the identity system that uniquely corresponds to the user account; and
using the unique token to sign in the user account to the application.
2. The method of claim 1 , wherein using the unique token allows the application to sign in the user account without receiving secure user data of the user account.
3. The method of claim 1 , further comprising:
receiving a cryptographic nonce with the unique token;
transmitting a sign-in request including the token and a value generated from the cryptographic nonce; and
receiving a sign-in confirmation.
4. The method of claim 1 , further comprising:
causing, by a second authorization module of a second application executing on the client device, a transmission of a second authorization request, including the identifier of the client device, to an identity system, wherein the second authorization request is transmitted for verification that the client device identified by the identifier corresponds to the user account;
receiving a second verification message based on the identifier of the client device, the second verification message comprising a second verification code;
providing the second verification code to the second authorization module;
causing, by the authorization module, a transmission of a confirmation of the second verification code to the identity system to authenticate the second application based on receiving the confirmation of the second verification code;
receiving a second unique token from the identity system that uniquely corresponds to the user account, wherein the second unique token is different from the token; and
using the second unique token to sign in the user account to the application.
5. The method of claim 1 , further comprising:
causing, by the authorization module, a transmission by the client device of a content item request from the application;
receiving a content item responsive to the content item request, wherein the content item is selected by the identity system based on secure user data of the user account; and
placing the content item within an interface of the application.
6. The method of claim 1 , further comprising:
receiving one or more additional unique tokens, each of the one or more additional unique tokens corresponding to user accounts using other instances of the application.
7. The method of claim 1 , wherein the verification message comprises a deep link referencing a location that includes the verification code.
8. A non-transitory computer readable storage medium comprising computer program instructions that when executed by a processor cause the processor to perform operations comprising:
causing, by an authorization module of an application executing on a client device, a transmission of an authorization request, including an identifier of the client device, to an identity system, wherein the authorization request is transmitted for verification that the client device identified by the identifier corresponds to a particular user account;
receiving, at the client device, a verification message generated by the identity system based on the identifier of the client device, the verification message comprising a verification code;
providing the verification code from the received verification message to the authorization module;
causing, by the authorization module, a transmission of a confirmation of the verification code to the identity system to authenticate the application based on receiving the confirmation of the verification code;
receiving a token from the identity system that uniquely corresponds to the user account; and
using the unique token to sign in the user account to the application.
9. The non-transitory computer readable storage medium of claim 8 , wherein using the unique token allows the application to sign in the user account without receiving secure user data of the user account.
10. The non-transitory computer readable storage medium of claim 8 , wherein the operations further comprise:
receiving a cryptographic nonce with the unique token;
transmitting a sign-in request including the token and a value generated from the cryptographic nonce; and
receiving a sign-in confirmation.
11. The non-transitory computer readable storage medium of claim 8 , wherein the operations further comprise:
causing, by a second authorization module of a second application executing on the client device, a transmission of a second authorization request, including the identifier of the client device, to an identity system, wherein the second authorization request is transmitted for verification that the client device identified by the identifier corresponds to the user account;
receiving a second verification message based on the identifier of the client device, the second verification message comprising a second verification code;
providing the second verification code to the second authorization module;
causing, by the authorization module, a transmission of a confirmation of the second verification code to the identity system to authenticate the second application based on receiving the confirmation of the second verification code;
receiving a second unique token from the identity system that uniquely corresponds to the user account, wherein the second unique token is different from the token; and
using the second unique token to sign in the user account to the application.
12. The non-transitory computer readable storage medium of claim 8 , wherein the operations further comprise:
causing, by the authorization module, a transmission by the client device of a content item request from the application;
receiving a content item responsive to the content item request, wherein the content item is selected by the identity system based on secure user data of the user account; and
placing the content item within an interface of the application.
13. The non-transitory computer readable storage medium of claim 8 , wherein the operations further comprise:
receiving one or more additional unique tokens, each of the one or more additional unique tokens corresponding to user accounts using other instances of the application.
14. The non-transitory computer readable storage medium of claim 8 , wherein the verification message comprises a deep link referencing a location that includes the verification code.
15. A system comprising a processor and a memory storing computer program instructions that when executed by the processor cause the processor to perform operations comprising:
causing, by an authorization module of an application executing on a client device, a transmission of an authorization request, including an identifier of the client device, to an identity system, wherein the authorization request is transmitted for verification that the client device identified by the identifier corresponds to a particular user account;
receiving, at the client device, a verification message generated by the identity system based on the identifier of the client device, the verification message comprising a verification code;
providing the verification code from the received verification message to the authorization module;
causing, by the authorization module, a transmission of a confirmation of the verification code to the identity system to authenticate the application based on receiving the confirmation of the verification code;
receiving a token from the identity system that uniquely corresponds to the user account; and
using the unique token to sign in the user account to the application.
16. The system of claim 15 , wherein using the unique token allows the application to sign in the user account without receiving secure user data of the user account.
17. The system of claim 15 , wherein the operations further comprise:
receiving a cryptographic nonce with the unique token;
transmitting a sign-in request including the token and a value generated from the cryptographic nonce; and
receiving a sign-in confirmation.
18. The system of claim 15 , wherein the operations further comprise:
causing, by a second authorization module of a second application executing on the client device, a transmission of a second authorization request, including the identifier of the client device, to an identity system, wherein the second authorization request is transmitted for verification that the client device identified by the identifier corresponds to the user account;
receiving a second verification message based on the identifier of the client device, the second verification message comprising a second verification code;
providing the second verification code to the second authorization module;
causing, by the authorization module, a transmission of a confirmation of the second verification code to the identity system to authenticate the second application based on receiving the confirmation of the second verification code;
receiving a second unique token from the identity system that uniquely corresponds to the user account, wherein the second unique token is different from the token; and
using the second unique token to sign in the user account to the application.
19. The system of claim 15 , wherein the operations further comprise:
causing, by the authorization module, a transmission by the client device of a content item request from the application;
receiving a content item responsive to the content item request, wherein the content item is selected by the identity system based on secure user data of the user account; and
placing the content item within an interface of the application.
20. The system of claim 15 , wherein the operations further comprise:
receiving one or more additional unique tokens, each of the one or more additional unique tokens corresponding to user accounts using other instances of the application.
21. The system of claim 15 , wherein the verification message comprises a deep link referencing a location that includes the verification code.