Authentication mechanism

A system comprising:

• a computer processor;
• an identity module executing on the computer processor and configured to enable the computer processor to:
• receive, from a client device, an authorization request originating from a first authorization module of a first application executing on the client device, wherein the authorization request comprises an identifier identifying the client device;
• cause, in response to the authorization request and based on the identifier, transmission of a verification message to the client device, wherein the verification message comprises a verification code;
• receive a confirmation of the verification code from the first authorization module of the first application executing on the client device;
• authenticate the first application based on the receiving the confirmation of the verification code;
• determine, after authenticating the first application, that the client device identified by the identifier corresponds to a user account including secure user data associated with a user;
• and
• transmit, to the first authorization module of the first application, a unique token verifying that the first application is authorized to sign into the user account, wherein:
• the unique token uniquely identifies the user account to the first application, and
• the secure user data is not shared with the first application.

A method comprising:

• transmitting, from a first authorization module of a first application executing on a client device, a first authorization request that includes an identifier identifying the client device, wherein the first authorization request is transmitted for verification that the client device identified by the identifier corresponds to a user account including secure user data associated with a user;
• receiving, at the first authorization module of the first application executing on the client device and in response to the first authorization request, a verification code;
• transmitting, from the first authorization module of the first application executing on the client device, a confirmation of the verification code;
• and
• receiving, at the first authorization module, a first unique token verifying that the first application is authorized to sign into the user account, wherein:
• the first unique token uniquely identifies the user account to the first application, and
• the secure user data is not shared with the first application.