Back to results
US 9,852,286 B2Granted
Automated password generation and change
AssigneeOkta, Inc.
InventorsHector Aguilar-Macias, Reman P. Child, Xin Gu, Jonathan R. Todd, Thomas M. Belote
Life of this patent
Estimating the term…
Loading patent…
Loading patent…
AssigneeOkta, Inc.
InventorsHector Aguilar-Macias, Reman P. Child, Xin Gu, Jonathan R. Todd, Thomas M. Belote
Estimating the term…
An identity management system detects the occurrence of a trigger event, such as a time period expiration, or an action on the identity management system. The identity management system accordingly generates a new password for an account of a user on a third-party service and causes the account of the user on the third-party service to use the new password. The identity management system may also a mobile device management system to configure a client of the user with the new password.
A computer-implemented method performed by an identity management system, the method comprising:
A non-transitory computer-readable storage medium having instructions executable by a processor, the instructions comprising:
A computer system comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
No references of this kind are recorded.
Authentication, i.e. establishing the identity or authorisation of security principals: structures or tools for the administration of authentication
User authentication: where a single sign-on provides access to a plurality of computers
Structures or tools for the administration of authentication: by designing passwords or checking the strength of passwords
For authentication of entities: providing single-sign-on or federations
About 8 years 7 months of term left · ends 27 May 2035 (estimated)
1. Technical Field
This application generally relates to the field of user account information and, in particular, to automated generation and change of passwords.
2. Background Information
FIG. 1 is a high-level block diagram illustrating an environment for generating and changing passwords in an automated manner, according to one embodiment.
FIG. 2 is a high-level block diagram illustrating an example of a computer for use as one or more of the entities illustrated in FIG. 1, according to one embodiment.
The Figures (FIGS.) and the following description describe certain embodiments by way of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles described herein. Reference will now be made to several embodiments, examples of which are illustrated in the accompanying figures. It is noted that wherever practicable similar or like reference numbers may be used in the figures and may indicate similar or like functionality.
FIG. 1 is a high-level block diagram illustrating an environment 100 for generating and changing passwords in an automated manner, according to one embodiment. The environment 100 may be maintained by an enterprise (e.g., an identity management service) that provides a password service that generates passwords for use with third-party service user accounts and interacts with third-party services to change passwords on user accounts. For example, an identity management system 120 generates a password and interacts with a third-party service system 140 to modify a user account so that the user account uses the newly-generated password. Since the password generation and change is automated, it is easy to use unique, secure passwords for each user account and change these passwords periodically.
As shown, the environment 100 includes a network 110, an identity management system 120, a client 130, a third-party service system 140, and a device management system 150. While one identity management system 120, one client 130, one third-party service system 140, and one device management system 150 are shown in the embodiment depicted in FIG. 1 for clarity, other embodiments can have different numbers of identity management systems, clients, third-party service systems, and device management systems.