Passing authentication information via parameters
Systems and methods for passing account authentication information via parameters. A server can provide, to a client device, an account parameter derived from an account credential used to authenticate a first application to insert into a link. The link can include an address referencing a second application. The account parameter can be passed from the first application to the second application responsive to an interaction on the link. The server can receive from the second application of the client device, subsequent to passing the account parameter from the first application to the second application, a request to authenticate the second application including the account parameter. The server can authenticate the client device for the second application using the account parameter. The server can transmit, responsive to authenticating the client device for the second application, an authentication indication to the second application of the client device.
1. A method for passing authentication information, the method comprising:
transmitting, by one or more processors of a client device to one or more servers, an account credential used to authenticate a first application;
receiving, by the one or more processors from the one or more servers, a link referencing a second application executing on the client device;
detecting, by the one or more processors, an interaction with the link;
obtaining, by the one or more processors, an account parameter generated using the account credential; and
passing, by the one or more processors, the account parameter to the second application, to cause the second application to request authentication from the one or more servers based on the account parameter.
2. The method of claim 1 , wherein obtaining the account parameter includes receiving the account parameter in the link, from the one or more servers.
3. The method of claim 1 , obtaining the account parameter includes:
determining that the link does not include the account parameter; and
generating the account parameter using the account credential.
4. The method of claim 3 , further comprising:
determining, by the one or more processors, a type of the account parameter; and
in response to determining that the type is obfuscated, generating an obfuscated parameter using two-way encryption of the account credential, the account parameter including the obfuscated parameter.
5. The method of claim 3 , further comprising:
determining, by the one or more processors, a type of the account parameter; and
in response to determining that the type is fingerprint:
generating a fingerprint parameter using one-way encryption of the account credential, the account parameter including the fingerprint parameter, and
storing the fingerprint parameter in a memory.
6. The method of claim 3 , further comprising:
determining, by the one or more processors, a type of the account parameter; and
in response to determining that the type is cache:
generating a credential token for identifying the account credential, the account parameter including the credential token, and
storing the credential token in a cache.
7. The method of claim 1 , wherein passing the account parameter to the second application includes using a Uniform Resource Locator (URI) protocol.
8. The method of claim 1 , wherein passing the account parameter to the second application includes using a function call.
9. A method for obtaining authentication information, the method comprising:
obtaining, by one or more processors of a client device from a first application executing on the client device, an account parameter used to authenticate the first application;
determining, by the one or more processors and based on the account parameter, an account credential;
transmitting, by the one or more processors to a server, the account credential; and
in response to receiving, from the server, authentication confirmation based on the account credential, applying, by the one or more processors, account settings to continue execution of a second application.
10. The method of claim 9 , wherein determining the account credential includes:
determining, by the one or more processors, a type of the account parameter; and
in response to determining that the type is obfuscated, transmitting an obfuscated account credential to the server.
11. The method of claim 9 , wherein determining the account credential includes:
determining, by the one or more processors, a type of the account parameter; and
in response to determining that the type is fingerprint, transmitting a fingerprinted account credential to the server.
12. The method of claim 9 , wherein determining the account credential includes:
determining, by the one or more processors, a type of the account parameter; and
in response to determining that the type is cache, retrieving the account credential from the cache.
13. A method of passing account authentication information via parameters, the method comprising:
receiving, by one or more processors of one or more servers and from a client device, an account credential used to authenticate a first application executing on the client device;
generating, by the one or more processors, an account parameter based on the account credential; and
providing, by the one or more processors and to the client device, the account parameter to insert into a link, wherein the link includes an address referencing a second application executable on the client device and is configured to cause the client device to pass the account parameter passed from the first application to the second application responsive to an interaction on the link.
14. The method of claim 13 , further comprising:
receiving, by the one or more processors, from the second application of the client device, subsequent to passing the account parameter from the first application to the second application, a request to authenticate the second application, the request including the account parameter;
authenticating, by the one or more processors, the client device for the second application using the account parameter provided to the first application and passed via the link to the second application; and
transmitting, by the one or more processors, based on authenticating the client device for the second application, an authentication indication identifying one of success or failure of authentication of the client device for the second application.
15. The method of claim 14 , wherein the authentication indication identifies success of authentication, and the method further comprises performing a full or partial login to an account on the second application using the account parameter.
16. The method of claim 14 , wherein the authentication indication identifies failure of authentication, and the second application is executed without using the account parameter to perform a full or partial login to an account of the second application.
17. The method of claim 14 , wherein providing the account parameter further comprises providing the account parameter derived from the account credential using a two-way encryption algorithm; and
wherein authenticating the client device for the second application further comprises recovering the account credential by applying the two-way encryption algorithm to the account parameter included in the request to authenticate.
18. The method of claim 14 , wherein providing the account parameter further comprises providing the account parameter derived from the account credential using a one-way encryption algorithm; and
wherein authenticating the client device for the second application further comprises determining that a second account parameter separately derived from the account credential using the one-way encryption algorithm matches the account parameter included in the request to authenticate.
19. The method of claim 14 , wherein authenticating the client device for the second application further comprises determining that the account parameter included in the request to authenticate matches the account parameter stored in a cache.