API Authorization Transformation via SSO Link

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network systems require users to perform multiple authorization processes to access services or functions, leading to increased resource usage and user friction, particularly when transitioning between public APIs and internal services or user experience sessions.

Innovation Solution

The implementation of an Open Authorization (OAuth) 2.0 protocol to transform API authorization across different authorization realms, allowing for seamless access to user experience sessions or internal services without requiring a second sign-on, by mapping permissions from public APIs to internal service permissions using access tokens and session tokens.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users access internal services or UX sessions from third-party applications, then service functionality is improved, but multiple authorization processes increase user friction and resource consumption

Engineering Contradiction:
Improveservice functionalityVSAvoiduser friction
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an authorization server as an intermediary that issues session tokens based on existing access tokens. This mediator enables seamless transition between third-party application context and internal service context without requiring users to perform multiple authorization actions, thus resolving the contradiction between service functionality and ease of operation

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary authorization by issuing access tokens through OAuth 2.0 flow before the user needs to access internal services. The authorization server then uses these pre-obtained access tokens to issue session tokens in advance, eliminating the need for repeated authorization processes and reducing user friction while maintaining service adaptability

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple authorization processes are implemented for accessing different services, then security coverage is improved, but resource consumption including processor cycles, network traffic, and memory usage increases

Engineering Contradiction:
Improvesecurity coverageVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple authorization processes into a single unified flow. The authorization server combines the verification of access tokens with the issuance of session tokens in one operation, maintaining comprehensive security coverage across different services while significantly reducing processor cycles, network traffic, and memory usage associated with separate authorization processes

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11368461B2Application programming interface authorization transformation system
Publication Date: 2022.06.21 EBAY INC
  • US11368461B2 patent drawing
  • US11368461B2 patent drawing
  • US11368461B2 patent drawing

AI summary

Systems and methods for transforming an API authorization to a UX session are provided. An authorization server receives, from a third-party application developed by a third-party, a request to access a user experience (UX) session on behalf of a user. The request comprises an access token previously granted by the authorization server to the third-party application in response to consent, by the user, to allow the third-party application to perform actions on behalf of the user. In one embodiment, this previous authorization comprises an Open Authorization (OAuth). In response to receiving the request the authorization server transforms the access token into a single sign on (SSO) link with a session token. The authorization server then returns the SSO link that includes the session token the third-party application hosted by the third-party. The SSO link causes the third-party application to redirect the user to the UX session corresponding to the SSO link.