SAML Single Sign-On Configuration via REST API

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing secure single sign-on solutions face challenges in providing secure authentication for users accessing web services due to the inherent insecurity of the Internet and limitations in configuration control for application developers, often requiring reliance on access management mechanisms that restrict flexibility and development capabilities.

Innovation Solution

The implementation of a method and system using a Representational State Transfer (REST) Application Programming Interface (API) for Secure Assertion Markup Language (SAML) protocols, which allows for secure validation and creation of SAML responses, enabling configuration control for application developers to manage trust relationships and identity providers without relying on access management mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access management mechanisms are used to provide secure authentication, then security is improved, but flexibility and development control for application developers deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidflexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a configuration file as an intermediary layer between the access management mechanism and the application developer. This configuration file contains trusted identity information and service provider names, allowing developers to control trust relationships without directly managing complex access management systems. The configuration file mediates between security requirements and developer flexibility, enabling secure single sign-on while maintaining adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If access management mechanisms are used to provide secure authentication, then security is improved, but device complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the essential security configuration elements (trusted identity information and service provider names) from the complex access management mechanism and places them into a separate, manageable configuration file. This extraction reduces the complexity burden on the application system while maintaining the security functionality through the configuration file's trusted identity information.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If configuration files with trusted identity information are used, then control over trust relationships is improved, but information security requirements become more stringent

Engineering Contradiction:
ImprovecontrolVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements preliminary action by pre-configuring trusted identity information and service provider names in the configuration file before runtime operations. This preliminary configuration establishes security boundaries and trust relationships in advance, reducing security risks during actual authentication operations. The configuration file is prepared with all necessary trusted identity information beforehand, eliminating the need for dynamic security decisions that could introduce vulnerabilities.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12160416B2System and method for secure single sign on using security assertion markup language
Publication Date: 2024.12.03 EXPRESS SCRIPTS STRATEGIC DEVELOPMENT INC
  • US12160416B2 patent drawing
  • US12160416B2 patent drawing
  • US12160416B2 patent drawing

AI summary

A method for providing secure single sign on includes receiving a first data object from an application hosting server, the first data object indicating at least a service provider name and identifying a configuration file corresponding to the service provider name, wherein the configuration file includes at least trusted identity information. The method also includes determining, using the configuration file corresponding to the service provider name, whether the first data object is valid and, in response to a determination that the first data object is valid, generating a response message.