Techniques for authentication via a mobile device
Techniques for authentication via a mobile device are provided. A mobile device is pre-registered for website authentication services. A user encounters a website displaying an embedded code as an image alongside a normal login process for that website. The image is identified by the mobile device, encrypted and signed by the mobile device and sent to a proxy. The proxy authenticates the code and associates it with the website. Credentials for the user are provided to the website to automatically authenticate the user for access to the website bypassing the normal login process associated with the website.
1. A method, comprising:
injecting a code into a login interface for a resource;
receiving a different code from a device in response to the device processing the code, wherein receiving further includes obtaining the different code as an encrypted and signed version of a number that is present in the code from the device;
authenticating a user that operates the device for access to the resource based at least in part on processing the different code;
obtaining registered credentials of the user when the user is successfully authenticated;
providing the registered credentials to the resource;
logging the user into an authenticated session with the resource using the registered credentials; and
providing a session handle to the user for the authenticated session between the user and the resource when the user is successfully authenticated, wherein the resource is incapable of performing authentication on the user via the code or the different code, and wherein the resource is a pre-existing and legacy resource that requires the registered credentials for authenticating the user.
2. The method of claim 1 further comprising, injecting a different code into the login interface page when the login interface is reloaded or rendered a different time.
3. The method of claim 1 , wherein injecting further includes randomly generating the code as an encrypted number embedded in a bar code or a Quick Response (QR) code.
4. The method of claim 1 , wherein injecting further includes providing the code to the login interface that is rendered on a different device from the device that provides the different code.
5. The method of claim 1 , wherein receiving further includes ensuring that an elapsed period of time from when the code was initially and first injected into the login interface is unexpired when receiving the different code.
6. The method of claim 1 , wherein providing further includes providing the session handle on a different device operated by the user from the device, wherein the login interface was rendered on the different device.
7. A system, comprising:
a server; and
a proxy configured to: i) execute on at least one processor of the server, ii) inject a unique and random encrypted code into a login interface of a resource each time the login interface is rendered; iii) authenticate a version of the unique and random encrypted code received from a user accessing the login interface, wherein the version represents the unique and random encrypted code that was decrypted and then encrypted and signed by a device of the user using a key associated with the device; iv) obtain registered credentials that were previously registered by the user based on successfully authenticating the version; v) log the user into an authenticated session with the resource by using the registered credentials; and vi) provide a session handle for the authenticated session between the user and the resource to the user, wherein the resource is incapable of performing authentication on the user via the unique and random encrypted code or the version of the unique and random encrypted code, and wherein the resource is a pre-existing and legacy resource that requires the registered credentials for authenticating the user.
8. The system of claim 7 , wherein the server is part of a cloud processing environment.