Outer Rim Archives
Archives · 2020 · 10536440

Granted patent

User account access management

Number
10536440
Published
2020-01-14
Filed
2017-10-23
Assignee
Disney Enterprises, Inc.
Inventors
Monibi; Mohamad H., Romanelli; Alexander
CPC
G06F21/1012; G06F21/1015; G06F21/62; H04L63/06; H04L63/083; H04L63/0838; H04L63/0853; H04L63/102
Verdict
Set aside account access management, security/business
Source
Google Patents · FreePatentsOnline

Abstract

A user account access management system includes a computing platform having a hardware processor and a system memory storing a user account access software code. The hardware processor executes the user account access software code to receive, from a first user device, a secondary account profile data for generating a secondary account associated with a primary user account registered with a web based service, and to receive, from a second user device, a sign up request for using the web based service. The hardware processor further executes the user account access software code to transmit an authentication token to one of the first user device and the second user device, receive the authentication token from the other of the first user device and the second user device, and link the secondary account with the second user device based on receiving the authentication code.

Background

BACKGROUND(1) There are situations in which a primary account holder may wish to enable other members of a group to have access to selected assets of the primary account. For example, in many households, one person, often a parent, is a primary account holder who owns and manages access to digital content, such as digital movie content. Access to the digital content is typically attached to that primary account holder's credentials. Sharing the digital content with other members of the family often involves giving full access to the primary account holder's credentials on devices used by other family members. Moreover, in instances where third-party Identity Providers (IDPs) such as Facebook® or Google® are used to authenticate a user, enabling access to the primary account may undesirably include providing full access to those third-party accounts as well.SUMMARY(2) There are provided systems and methods for managing user account access, substantially as shown in and/or described in connection with at least one of the figures, and as set forth more completely in the claims.

Claims

1. A user account access management system, the system comprising: a computing platform having a hardware processor and a system memory storing a user account access software code; the hardware processor configured to execute the user account access software code to: receive, from a first user device authenticated on a primary user account, a secondary account profile data for generating a secondary account associated with the primary user account registered with a web based service; receive, from a second user device not authenticated on the secondary account, a sign up request to link the secondary account with the second user device for using the second user device to access assets of the primary user account via the web based service, the secondary account profile data including restrictions for accessing the assets of the primary user account; transmit, in response to the sign up request, an authentication token to the first user device; receive the authentication token from the second user device; and link the secondary account with the second user device based on receiving the authentication token from the second user device, wherein linking the secondary account with the second user device includes locking access to the assets of the primary user account by the second user device based on the restrictions included in the secondary account profile data. 7. A method for use by a user account access management system including a hardware processor and a system memory storing a user account access software code, the method comprising: receiving from a first user device authenticated on a primary user account, using the hardware processor, a secondary account profile data for generating a secondary account associated with the primary user account registered with a web based service; receiving from a second user device not authenticated on the secondary account, using the hardware processor, a sign up request to link the secondary account with the second user device for using the second user device to access assets of the primary user account via the web based service, the secondary account profile data including restrictions for accessing the assets of the primary user account; transmitting, in response to the sign up request and using the hardware processor, an authentication token to the first user device; receiving, using the hardware processor, the authentication token from the second user device; and linking, using the hardware processor, the secondary account with the second user device based on receiving the authentication token from the second user device, wherein linking the secondary account with the second user device includes locking access to the assets of the primary user account by the second user device based on the restrictions included in the secondary account profile data. 13. A computer-readable non-transitory medium having stored thereon instructions, which when executed by a hardware processor of a user account access management system, instantiate a method comprising: receiving, from a first user device authenticated on a primary user account, a secondary account profile data for generating a secondary account associated with the primary user account registered with a web based service; receiving, from a second user device not authenticated on the secondary account, a sign up request for using the web based service a sign up request to link the secondary account with the second user device for using the second user device to access assets of the primary user account via the web based service, the secondary account profile data including restrictions for accessing the assets of the primary user account; transmitting, in response to the sign up request, an authentication token to the first user device; receiving the authentication token from the second user device; and linking the secondary account with the second user device based on receiving the authentication token from the second user device, wherein linking the secondary account with the second user device includes locking access to the assets of the primary user account by the second user device based on the restrictions included in the secondary account profile data.