Automatic account management and device registration
A single sign-on system accepts master credentials from a user device and/or application, and automatically signs on to supported services using account credentials corresponding to those services. If the user has not created an account used by a particular device or application, the system can automatically interact with the account service to create the account. Similarly, if the device or application that relies on the account has not already been registered with the account, the system automatically interacts with the account to register the device or account.
1. A computer-implemented method comprising:
under control of one or more processors configured with executable instructions which, in response to being performed by the one or more processors perform actions including:
storing a first data structure that includes a device identifier, and an application identifier associated with a master account;
storing a second data structure that includes an account service identifier associated with the master account;
receiving, from a device, a sign-on request for a device application that relies on a user account for an account service, wherein the sign-on request indicates a device identifier of the device, an application identifier of the device application, and an account service identifier of the account service;
receiving master credentials in order to access the entries stored in the master account; authenticating based at least in part on master credentials associated with the master account in order to access entries associated with the master account;
determining whether an entry exists within a first data structure that specifies the same device identifier and the application identifier indicated in the sign-on request;
signing on to the user account with respect to the device application in response to determining that the first data structure specifies the device identifier and the application identifier indicated in the sign-on request; and
in response to determining that one or more of the device identifier or the application identifier does not exist within the first data structure,
determining whether there is an existing entry in a second data structure that specifies the account service associated with the account service identifier,
in response to determining that there is the existing entry in the second data structure that corresponds to the same account service identifier indicated in the sign-on request, creating one or more entries in the first data structure to specify the device identifier, the application identifier, and the account service identifier,
in response to determining that there is not an existing entry of the account service identifier in the second data structure, creating one or more entries in the second data structure to add the user account for the account service, and
signing on to the user account to access the account service.
2. The computer-implemented method of claim 1 , wherein the device application comprises a native device element.
3. The computer-implemented method of claim 1 , wherein signing on to the user account with respect to the device application is performed with stored account credentials corresponding to the user account.
4. The computer-implemented method of claim 1 , wherein signing on to the user account with respect to the device application is performed with stored account credentials other than the master credentials.
5. The computer-implemented method of claim 1 , further comprising:
soliciting the user for account credentials corresponding to the user account; and
storing the solicited account credentials.
6. The computer-implemented method of claim 1 , wherein the actions are performed in cooperation by a client component and an online server.
7. The computer-implemented method of claim 1 , wherein the actions are performed in cooperation with an application plug-in component.
8. The computer-implemented method of claim 1 , wherein the actions are performed in cooperation with a device component.
9. The computer-implemented method of claim 1 , wherein the actions are performed in cooperation with an online server.
10. The computer-implemented method of claim 1 , further comprising soliciting a user for information to be associated with the user account.
11. The computer-implemented method of claim 1 , further comprising soliciting a user for a user identification to be associated with the user account.
12. A system comprising:
one or more hardware processors;
one or more computer-readable media containing instructions that are executable by the one or more hardware processors to perform actions comprising:
storing a first data structure that includes a device identifier, and an application identifier associated with a master account;
storing a second data structure that includes an account service identifier associated with the master account;
receiving, from a device, a sign-on request for a device application that relies on a user account for an account service, wherein the sign-on request indicates a device identifier of the device, an application identifier of the device application, and an account service identifier of the account service;
receiving master credentials in order to access the entries stored in the master account;
authenticating based at least in part on master credentials associated with the master account in order to access entries associated with the master account;
determining whether an entry exists within a first data structure that specifies the same device identifier and the application identifier indicated in the sign-on request;
signing on to the user account with respect to the device application in response to determining that the first data structure specifies the device identifier and the application identifier indicated in the sign-on request; and
in response to determining that one or more of the device identifier or the application identifier does not exist within the first data structure,
determining whether there is an existing entry in a second data structure that specifies the account service associated with the account service identifier,
in response to determining that there is the existing entry in the second data structure that corresponds to the same account service identifier indicated in the sign-on request,
creating one or more entries in the first data structure to specify the device identifier, the application identifier, and the account service identifier,
in response to determining that there is not an existing entry of the account service identifier in the second data structure, creating one or more entries in the second data structure to add the user account for the account service, and
signing on to the user account to access the account service.
13. The system of claim 12 , wherein the device application comprises a native device element.
14. The system of claim 12 , wherein signing on to the user account with respect to the device application is performed with stored account credentials other than the master credentials.
15. The system of claim 12 , wherein the actions are performed in cooperation by a client component and an online server.
16. The system of claim 12 , wherein the actions are performed in cooperation with an application plug-in component.
17. The system of claim 12 , wherein the actions are performed in cooperation with a device component.
18. The system of claim 12 , wherein the actions are performed in cooperation with an online server.
19. The system of claim 12 , wherein the actions further comprise soliciting a user for information to be associated with the user account.
20. The system of claim 12 , wherein the actions further comprise soliciting a user for a user identification to be associated with the user account.
21. A non-transitory computer-readable storage medium to store computer-executable instructions which, in response to being performed by a computing device, cause the computing device to perform actions comprising:
storing a first data structure that includes a device identifier, and an application identifier associated with a master account;
storing a second data structure that includes an account service identifier associated with the master account;
receiving, from a device, a sign-on request for a device application that relies on a user account for an account service, wherein the sign-on request indicates a device identifier of the device, an application identifier of the device application, and an account service identifier of the account service;
receiving master credentials in order to access the entries stored in the master account;
authenticating based at least in part on master credentials associated with the master account in order to access entries associated with the master account;
determining whether an entry exists within a first data structure that specifies the same device identifier and the application identifier indicated in the sign-on request;
signing on to the user account with respect to the device application in response to determining that the first data structure specifies the device identifier and the application identifier indicated in the sign-on request; and
in response to determining that one or more of the device identifier or the application identifier does not exist within the first data structure,
determining whether there is an existing entry in a second data structure that specifies the account service associated with the account service identifier,
in response to determining that there is the existing entry in the second data structure that corresponds to the same account service identifier indicated in the sign-on request, creating one or more entries in the first data structure to specify the device identifier, the application identifier, and the account service identifier,
in response to determining that there is not an existing entry of the account service identifier in the second data structure, creating one or more entries in the second data structure to add the user account for the account service, and
signing on to the user account to access the account service.
22. The non-transitory computer-readable storage medium of claim 21 , wherein the device application comprises a native device element.
23. The non-transitory computer-readable storage medium of claim 21 , wherein signing on to the user account with respect to the device application is performed with stored account credentials other than the master credentials.
24. The non-transitory computer-readable storage medium of claim 21 , wherein the actions are performed in cooperation by a client component and an online server.
25. The non-transitory computer-readable storage medium of claim 21 , wherein the actions are performed in cooperation with an application plug-in component.
26. The non-transitory computer-readable storage medium of claim 21 , wherein the actions are performed in cooperation with a device component.
27. The non-transitory computer-readable storage medium of claim 21 , wherein the actions are performed in cooperation with an online server.
28. The non-transitory computer-readable storage medium of claim 21 , wherein the actions further comprise soliciting a user for information to be associated with the user account.
29. The non-transitory computer-readable storage medium of claim 21 , wherein the actions further comprise soliciting a user for a user identification to be associated with the user account.