US 2020/0007541 A1Published application

Registration of the same domain with different cloud services networks

AssigneeMicrosoft Technology Licensing, LLC

InventorsMadan R. Appiah, Maciej J. Cupial

Life of this patent

Estimating the term…

Loading patent…

Abstract

Embodiments described herein are directed to the registration of the same domain with different cloud services networks. For example, systems and methods described herein enable registering a domain in a cloud services network wherein the same domain is also concurrently registered in another cloud services network. Systems and methods described herein further enable selecting one of a plurality of cloud-based identity providers to process a request to authenticate a user associated with a domain that is registered in more than one cloud services network and generating an authentication response in accordance with the selection. Systems and methods described herein also enable the federation of user authentication requests from different cloud services networks to the same enterprise identity provider.

Claims20

Dependent claims

A system including:

a first cloud services network including:
a first plurality of computing devices;
a first resource endpoint implemented on one or more computing devices in the first plurality of computing devices, the first resource endpoint being configured to:
receive a resource request associated with a user, the resource request requesting access to a resource of the first cloud services network;
issue an authentication request to a first identity provider of the first cloud services network in response to receiving the resource request;
the first identity provider implemented on one or more computing devices in the first plurality of computing devices, the first identity provider being configured to:
identify a domain associated with the user;
access a data structure stored by the first cloud services network that identifies a plurality of cloud services networks with which the domain is registered and that stores metadata associated with the domain for each cloud services network in the plurality of cloud services networks;
based on the metadata, determine whether the authentication request should be processed by the first identity provider or by a second identity provider within a second cloud services network in the plurality of cloud services networks;
in response to determining that the authentication request should be processed by the first identity provider, authenticate the user associated with the resource request to generate a first authentication response and send the first authentication response to the first resource endpoint;
in response to determining that the authentication request should be processed by the second identity provider,
redirect the authentication request to the second identity provider to process the authentication request, generate a second authentication response and send the second authentication response to the first identity provider;
and
receive the second authentication response from the second identity provider, generate a third authentication response based on the second authentication response, and provide the third authentication response to the first resource endpoint.

11 more elements

A computer-implemented enterprise identity provider, comprising:

one or more processing circuits;
one or more memory devices connected to the one or more processing circuits, the one or more memory devices storing computer program instructions that when executed by the one or more processing circuits cause the one or more processing circuits to perform operations, the operations including:
receiving a first user authentication request from a first cloud-based identity provider associated with a first cloud services network, the first user authentication request seeking authentication of a user associated with a domain;
processing the first user authentication request based on credential information associated with the user and stored by the enterprise identity provider to generate a first federated token;
and
transmitting the first federated token to the first identity provider;
receiving a second user authentication request from a second cloud-based identity provider associated with a second cloud services network, the second user authentication request seeking authentication of the user associated with the domain;
processing the second user authentication request based on the user credential information associated with the user and stored by the enterprise identity provider to generate a second federated token;
and
transmitting the second federated token to the second identity provider.

7 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/145,532Filed 28 Sep 2018
Priority: 29 Jun 2018
Published: 2 Jan 2020
Term ends: Not estimatedThe source records don’t support an estimate.

Classification10 codes

H04L 63/08
Network architectures or network communication protocols for network security: for authentication of entities
H04L 63/0884
For authentication of entities: by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity…
G06F 21/6218
Protecting access to data via a platform, e.g. using keys or access control rules: to a system of files or objects, e.g. local or distributed file…
H04L 61/3015
Managing network names, e.g. use of aliases or nicknames: name registration, generation or assignment

Family

Application62/692,320Us provisional application · filed 29 Jun 2018
US 10,749,868 B2Related patent
US 2020/0007541 A1This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key