Partner Web Service Token Authentication via Intermediary Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for securing partner-enabled web services are insecure due to challenges in verifying the origin of requests from partner applications, leading to potential security breaches and mistrust in service requests from partners.

Innovation Solution

A method and system that generate a token with a unique signature for a partner application, allowing the partner service to verify the authenticity of the request, associating the user with the partner application and enabling independent regeneration of the signature, which is sent to the browser client, using proprietary authentication utilities and a one-way hashing algorithm to ensure secure access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If direct access to partner-enabled web service is allowed from browser client, then ease of operation is improved, but security is worsened

Engineering Contradiction:
Improveease of accessVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a partner application as an intermediary component between the browser client and the partner-enabled web service. The partner application generates tokens that associate the user with the partner application, enabling the browser client to access the web service securely through this intermediary layer rather than directly, thus maintaining ease of operation while improving security

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary authentication by requiring the partner application to generate a token with signature before the browser client can access the web service. This preliminary action of token generation and signature creation ensures that the web service can verify the authenticity of requests in advance, resolving the security concern while allowing direct browser access

Inventive Principle:
Principle #10Preliminary action

2Reliability

If server-to-server communication is used for partner applications, then security is improved, but ease of operation is worsened

Engineering Contradiction:
ImprovesecurityVSAvoidease of access
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent makes the partner application multi-functional by enabling it to serve both as a security verification mechanism (generating tokens with signatures) and as a user interface (accessible through browser client). This universality allows the system to maintain server-to-server security protocols while also providing ease of browser-based access to end users

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The partner application acts as an intermediary that bridges server-to-server communication security with browser client accessibility. It generates tokens that enable the browser client to securely access the web service without requiring direct server-to-server communication, thus maintaining security while improving ease of operation

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10320796B2Securing partner-enabled web service
Publication Date: 2019.06.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10320796B2 patent drawing
  • US10320796B2 patent drawing
  • US10320796B2 patent drawing

AI summary

The claimed subject matter provides a method for securing a partner service. The method can include receiving a request, wherein the request comprises a unique value, to access the partner service, wherein the request is received from a browser client for a partner application and determining that a user is authorized to access the partner application, the partner application generating a token that associates the user with the partner application. The method can also include generating a signature for the token, the signature to enable the partner service to independently regenerate the signature, the token comprising an identifier for the partner application enabling the partner service to detect which partner application generates the token and sending the token with the signature to the browser client.