Portal Application Mediator for SSO Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face inconvenience when accessing applications that are not integrated with their single-sign-on (SSO) solutions, requiring manual authentication each time, which reduces the benefits of SSO in the overall user experience.

Innovation Solution

A method where an authentication server assigns a unique request token and loads a script to a user device's operating system component, such as WEBVIEW, to launch a portal application that stores credentials, allowing seamless authentication for third-party applications without manual credential entry, even if they are not available within the portal application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users access third-party applications not integrated with SSO, then they can use diverse applications, but they must manually enter credentials each time

Engineering Contradiction:
Improveapplication compatibilityVSAvoidauthentication convenience
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a portal application as an intermediary between the user and third-party applications. The portal application captures authentication requests from any application, manages credentials centrally, and performs authentication on behalf of the user. This mediator enables SSO functionality across applications without requiring each application to be integrated with the SSO system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The portal application serves multiple functions: it acts as an authentication manager, credential storage system, and application launcher. By consolidating these functions in a single universal application, the system provides SSO capabilities across diverse applications without requiring individual application modifications.

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

2Ease of operation

If portal application manages all authentication, then SSO benefit is improved, but third-party applications not in portal cannot be accessed

Engineering Contradiction:
Improveauthentication convenienceVSAvoidapplication access scope
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The portal application serves as an intermediary that intercepts authentication requests from any application, including third-party applications not pre-configured in the portal. It dynamically manages credentials and performs authentication on behalf of the user, enabling access to applications outside the traditional SSO framework.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If manual credential entry is required, then security control is improved, but user experience deteriorates

Engineering Contradiction:
Improvesecurity controlVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The portal application implements self-service authentication by automatically managing credential storage, retrieval, and submission. The system handles the authentication process autonomously without requiring user intervention, while maintaining security through centralized credential management and validation protocols.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11809529B2Systems and methods for improved authentication
Publication Date: 2023.11.07 OMNISSA LLC
  • US11809529B2 patent drawing
  • US11809529B2 patent drawing
  • US11809529B2 patent drawing

AI summary

When a user attempts to access a first application installed on a user device, it can send an authentication request to an authentication server. The authentication server can assign a unique request token to the request and load a script to a component of the operating system executing on the user device that displays content within the first application. The script can cause a portal application to launch on the user device. The portal application can send a request to the authentication server on behalf of the user, including the unique request token and an access token stored by, or accessible to, the portal application. The authentication server can receive the request from the portal application and validate the request based on the unique request token and the access token. Upon validating the request, the authentication server can authenticate the user at the first application.