Local IDAAS Proxy SSL Channel for SaaS Application Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for connecting local applications with SaaS applications are cumbersome and intrusive, particularly due to network addressing inconsistencies, and transferring the IDAAS server into the local network is incompatible.

Innovation Solution

A method and system using a local IDAAS proxy in the local network to establish an SSL connection with an SSL access point in an IDAAS network, allowing communication via a private network, without requiring additional devices or modifying network architecture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a VPN is used to connect local and SaaS applications, then communication between the applications is enabled, but the solution becomes very intrusive and difficult to implement due to network addressing inconsistencies

Engineering Contradiction:
Improvecommunication capabilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an IDAAS proxy as an intermediary component deployed in the local network. This proxy acts as a mediator between local applications and the remote IDAAS server, handling authentication and communication without requiring complex network configuration or VPN setups. The proxy simplifies the connection by absorbing the complexity of network addressing inconsistencies.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the communication architecture into distinct components: local applications, local IDAAS proxy, remote IDAAS server, and SaaS applications. This segmentation allows each component to operate independently with well-defined interfaces, reducing the complexity of integrating different network addressing schemes while maintaining communication capability.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If the IDAAS server is transferred into the local network, then communication with local applications is simplified, but this is incompatible with the very use of the IDAAS server

Engineering Contradiction:
Improvecommunication simplicityVSAvoidIDAAS server compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

Instead of moving the IDAAS server into the local network, the patent uses an IDAAS proxy as an intermediary that replicates the server's authentication functionality locally. This proxy maintains compatibility with the remote IDAAS server while providing local access simplicity, allowing the server to remain in its original location.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a local copy of the IDAAS server's authentication functionality through the IDAAS proxy. This copy handles local authentication requests and communicates with the remote server when necessary, providing the simplicity of local operation while maintaining the adaptability of cloud-based architecture.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If additional devices are added to enable communication between local and SaaS applications, then communication capability is achieved, but implementation costs and architectural complexity increase

Engineering Contradiction:
Improvecommunication capabilityVSAvoidimplementation cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The IDAAS proxy is designed to perform multiple functions: it handles authentication for local applications, establishes secure connections to the remote IDAAS server, and facilitates communication with SaaS applications. By making the proxy multi-functional, the patent avoids the need for separate dedicated devices for each function, reducing overall implementation costs.

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

Solution Approach 2:

The IDAAS proxy is implemented as a software component that can run on existing servers or devices in the local network, eliminating the need for specialized hardware. The system uses existing network infrastructure and authentication mechanisms, allowing the proxy to serve itself and other components without requiring additional expensive equipment.

Inventive Principle:
Principle #25Self-service

Applied Scientific Principles

This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.

Function Achieved in This Case

Enables secure, simplified communication between local and SaaS applications, maintaining network security and reducing implementation costs while avoiding architectural intrusion.

Implementation Method 1

generating, by a proxy, so-called local IDAAS proxy, located in said local network, an SSL connection associated: with said SSL access point in said IDAAS network, and with a port for communicating with said local application in said local network

Methodology Applied
Scientific EffectSSL encryption:

Data Source

PatentUS12526267B2Method for creating a communication channel between a location application and an SaaS application, and method and system for communicating between the applications
Publication Date: 2026.01.13 BULL SA
  • US12526267B2 patent drawing
  • US12526267B2 patent drawing

AI summary

The invention relates to a method for creating a communication channel between a local application executed in a local network and a remote SaaS application. The method includes generating an SSL access point and associating the SSL access point to a communication port with the SaaS application. The method also includes generating, by a proxy, a local IDAAS proxy, located in the local network, and an SSL connection associated with the SSL access point and associated with a port for communicating with the local application in the local network. The invention also relates to a method and a system for communicating between the local application and the SaaS application.