Loading patent…
AssigneeOkta, Inc.
InventorsReman P. Child, Hassen Karaa, Xin Gu, Hector Aguilar-Macias, Andrew P. Drozdov
Estimating the term…
An identity management system provides single sign-on (SSO) services to clients, logging the clients into a variety of third-party services for which the clients have accounts. An SSO integration is stored for each of the third-party services, the SSO integration including information that allows the identity management system to automate the login for the corresponding third-party service, such as locations of the login pages, and/or identities of username and password fields. The identity management system uses different techniques in different embodiments to detect that a given SSO integration is broken (i.e., no longer permits login for its corresponding third-party service) and/or to repair the SSO integration.
A computer-implemented method performed by an identity management system, the method comprising:
A computer-implemented method performed by an identity management system, the method comprising:
A computer-implemented method performed by an identity management system, the method comprising:
A computer-implemented method performed by an identity management system, the method 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.
For authentication of entities: providing single-sign-on or federations
User authentication: where a single sign-on provides access to a plurality of computers
Protocols: based on web technology, e.g. hypertext transfer protocol [HTTP]
Digital communication
About 9 years 9 months of term left · ends 29 Jul 2036 (estimated)
1. Technical Field
This application generally relates to the field of user account information and, in particular, to detection and repair of broken single sign-on integration with third-party services over a computer network.
2. Background Information
FIG. 1 is a high-level block diagram illustrating an environment for detecting and repairing a broken single sign-on integration, 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.
FIG. 3 is a high-level block diagram illustrating a detailed view of the single sign-on (SSO) troubleshooting module from 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 detecting and repairing a broken single sign-on (SSO) integration, according to one embodiment. The environment 100 may be maintained by an enterprise (e.g., an identity management service) that provides a SSO troubleshooting service that detects and/or repairs broken SSO integrations. For example, an identity management system 120 detects that an existing SSO integration is broken such that an SSO service can no longer automatically sign in a user (using a client 130) to a third-party service user account (managed by a third-party service system 140). As another example, an identity management system 120 repairs a broken SSO integration such that an SSO service can once again automatically sign in a user (using a client 130) to a third-party service user account (managed by a third-party service system 140).
As shown, the environment 100 includes a network 110, an identity management system 120, a client 130, and a third-party service system 140. While one identity management system 120, one client 130, and one third-party service system 140 are shown in the embodiment depicted in FIG. 1 for clarity, other embodiments can have different numbers of identity management systems, clients, and third-party service systems.