# US 2023/0412582 A1 · Systems and methods for Single Sign On (SSO) redirecting in the presence of multiple service providers for a cloud service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0412582 A1
- Document ID: US20230412582A1
- Status: Published application
- Kind: A1
- Application number: 17/751,175
- Filed: 2022-05-23
- Published: 2023-12-21
- Earliest claimed: 2022-05-23
- Assignees: Plume Design, Inc.
- Applicants: Plume Design, Inc.
- Inventors: Thomas F. Price; Crystal Wai
- Web page: https://patentgrep.com/patent/US20230412582A1

## CPC

- H04L 63/0815: {providing single-sign-on or federations}
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- G06F 21/41: where a single sign-on provides access to a plurality of computers
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 47/70: Admission control; Resource allocation
- H04L 63/0838: {using one-time-passwords}
- H04L 63/0846: {using time-dependent-passwords, e.g. periodically changing passwords}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present disclosure relates to systems and methods for SSO redirecting. More particularly, for identifying and authenticating a user via the user's specific service provider. A user intending to establish a connection between two cloud services, where the user is subscribed to a specific service provider in one cloud service, must provide identity authentication and consent to the cloud service. The processes described herein provide the user with an authentication token supplied by the user's specific service provider associated with a first cloud service. Utilizing the authentication token, the token being entered into a URL opened within the second cloud service, the first cloud service can identify the service provider with which the user is associated, and provide the user with means of identification authentication. Further, the URL provides the first cloud service with information for the connection to the second cloud service.

## Claims

### Claim 1

A method implemented by a first and second cloud service, the method comprising steps of:
responsive to a user requesting to connect the first and second cloud, the second cloud presenting to the user a Uniform Resource Locator (URL) to a web page having a field for the user to input an authorization token, the authorization token provided responsive to the user selecting a feature on a first cloud service for connecting the first and second cloud;
receiving the authorization token;
identifying a service provider associated with the user based on the authorization token;
presenting the user with a login associated with the identified service provider; and
responsive to a successful login, allowing a connection between the first cloud service and second cloud service.

### Claim 2 (depends on 1)

The method of claim 1, wherein the service provider is one of a plurality of service providers for the first cloud service.

### Claim 3 (depends on 1)

The method of claim 1, wherein the feature of the second cloud service enables the second cloud service to control aspects of the first cloud service.

### Claim 4 (depends on 1)

The method of claim 1, wherein the authorization token is encoded with information, including information about the user's identity or information about which service provider is associated with the user.

### Claim 5 (depends on 1)

The method of claim 1, wherein the authorization token is a code provided to the user by an application associated with the service provider.

### Claim 6 (depends on 5)

The method of claim 5, wherein the code is a temporary code which cycles to reduce security risks.

### Claim 7 (depends on 5)

The method of claim 5, wherein the code is generated at the time the user accesses the application or generated by a specific action to trigger the generation of the code.

### Claim 8 (depends on 1)

The method of claim 1, wherein the service provider is an Identity Provider (IDP) for the first cloud service.

### Claim 9 (depends on 1)

The method of claim 1, wherein the URL provided to the user is specific to the second cloud service, and the URL is operated by the first cloud service.

### Claim 10 (depends on 1)

The method of claim 1, wherein the first cloud service is a home network, and the second cloud service is a smart home service enabled to control the home network.

### Claim 11 (depends on 1)

The method of claim 1, wherein the first cloud service is a home network, and the second cloud service is a wellness, health, personal wellbeing, fitness, or exercise application.

### Claim 12 (depends on 1)

The method of claim 1, wherein the first cloud service is a home network, and the second cloud service is a utility, energy, power consumption monitoring, or power usage control application.

### Claim 13

A method implemented by a first and second cloud service, the method comprising steps of:
responsive to a user requesting to connect the first and second cloud, the second cloud presenting to the user a Uniform Resource Locator (URL) to a web page having a field for the user to input an authorization token, the authorization token provided responsive to the user selecting a feature on a first cloud service for connecting the first and second cloud;
receiving the authorization token, the authorization token having encoded within it the credentials required to connect the two clouds; and
responsive to successfully receiving the authorization token, allowing a connection between the first cloud service and second cloud service.

### Claim 14 (depends on 13)

The method of claim 13, wherein a service provider is identified based on the authorization token, and wherein the service provider is one of a plurality of service providers for the first cloud service.

### Claim 15 (depends on 13)

The method of claim 13, wherein the feature of the second cloud service enables the second cloud service to control aspects of the first cloud service.

### Claim 16 (depends on 13)

The method of claim 13, wherein the authorization token is encoded with information, including information about the user's identity or information about which service provider is associated with the user.

### Claim 17 (depends on 13)

The method of claim 13, wherein the authorization token is a code provided to the user by an application associated with the first cloud service.

### Claim 18 (depends on 17)

The method of claim 17, wherein the code is a temporary code which cycles to reduce security risks.

### Claim 19 (depends on 17)

The method of claim 17, wherein the code is generated at the time the user accesses the application or generated by a specific action to trigger the generation of the code.

### Claim 20 (depends on 13)

The method of claim 13, wherein the URL provided to the user is specific to the second cloud service, and the URL is operated by the first cloud service.

### Claim 21 (depends on 13)

The method of claim 13, wherein the first cloud service is a home network, and the second cloud service is a smart home service enabled to control the home network.

### Claim 22 (depends on 13)

The method of claim 13, wherein the first cloud service is a home network, and the second cloud service is a wellness, health, personal wellbeing, fitness, or exercise application.

### Claim 23 (depends on 13)

The method of claim 13, wherein the first cloud service is a home network, and the second cloud service is a utility, energy, power consumption monitoring, or power usage control application.
