SSO Proxy for Non-Compliant Application Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-SSO-compliant applications require internal modifications to adapt to changes in SSO protocols, making it difficult to integrate them seamlessly into an SSO framework without frequent updates.
Innovation Solution
A system and method that uses an SSO proxy to forward user credentials to an SSO server for authentication, generating an SSO token, and providing it to non-SSO-compliant applications, allowing them to function within an SSO system without internal modifications, by encapsulating user names and passwords in HTTP requests and authenticating them using SSO protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-SSO-compliant applications are modified internally to implement SSO mechanisms, then they can function within an SSO framework, but they require modifications each time there is a change to the SSO protocol at the SSO server level
Solution Approach 1:
An SSO proxy is introduced as an intermediary component between non-SSO-compliant applications and the SSO server. The proxy handles the translation and encapsulation of authentication requests, allowing applications to remain unchanged while still benefiting from SSO functionality. When SSO protocols change, only the proxy needs updating, not the applications themselves.
Solution Approach 2:
The system is divided into distinct functional components: the SSO proxy handles protocol-specific operations, while applications maintain their original functionality. This segmentation isolates protocol change impacts to the proxy layer, protecting applications from modification requirements.
2Ease of operation
If all security algorithms are centralized in a single SSO server, then authentication is standardized and simplified, but non-SSO-compliant applications cannot access the system without internal modifications
Solution Approach 1:
The SSO proxy serves as a mediator that bridges the gap between centralized authentication and legacy applications. It receives authentication requests from non-SSO applications, encapsulates them in SSO-compliant formats, forwards them to the SSO server, and handles the response, thus maintaining both simplicity and compatibility.
Solution Approach 2:
The proxy creates encapsulated copies of authentication requests in SSO-compliant formats, allowing the SSO server to process them without requiring the original applications to understand or implement SSO protocols directly.
3Reliability
If applications are modified to implement SSO mechanisms, then they can participate in SSO authentication, but maintenance burden increases when SSO protocols change
Solution Approach 1:
By positioning the SSO proxy as the sole point of contact for protocol implementation, maintenance efforts are concentrated in one location. When SSO protocols change, the proxy is updated to handle the new protocols, while applications continue to function without modification, significantly reducing overall maintenance burden.
Data Source
AI summary
A method for providing SSO authentication when accessing non-SSO-compliant applications, the method including forwarding a user name and a password received from a non-SSO-compliant application to an SSO proxy, encapsulating the user name and password in a request to access a protected application, authenticating the user name and password responsive to the request using SSO authentication, and generating an SSO token if said authentication step is successful.