Proxy-Mediated Software Authentication and Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software authentication and authorization systems face challenges when using standard identity provider protocols, especially when integrating open-source or vendor software, necessitating a mechanism for a proxy service as an intermediary to manage authentication and authorization.
Innovation Solution
A method and system utilizing a proxy service as an intermediary that employs Natural Language Processing (NLP) and Natural Language Understanding (NLU) concepts to authenticate and authorize software by generating identity and service provider requests through application programming interfaces (APIs), enabling verification and data filtering based on user authorization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If standard identity provider protocols are used for authentication and authorization, then integration with existing systems is simplified, but open-source or vendor software cannot be made operational
Solution Approach 1:
The patent introduces a proxy service as an intermediary component between the identity provider and the software application. This proxy service receives authentication requests from the application, translates them into standard identity provider protocol formats, communicates with the identity provider, and translates the responses back. This intermediary approach enables open-source or vendor software to operate with standard identity providers without requiring the software itself to implement complex protocol handling, thus resolving the contradiction between software compatibility and system complexity.
2Reliability
If a controlled authentication and authorization layer is built on top of standard identity provider protocols, then security and control are improved, but feasibility of making new software operational is reduced
Solution Approach 1:
The proxy service acts as a controlled layer that sits between the identity provider and applications. It implements the authentication and authorization logic, filtering and validating tokens before allowing access. This controlled layer provides security and reliability while maintaining ease of software deployment because the control logic is centralized in the proxy service rather than requiring each application to implement its own authentication layer.
Solution Approach 2:
The authentication system is segmented into distinct functional components: the identity provider that handles token issuance, the proxy service that handles validation and control logic, and the applications that consume authenticated services. This segmentation allows each component to be developed and deployed independently, improving both reliability through specialized control and ease of manufacture through modular deployment.
3Productivity
If direct connection between client and service provider is established, then communication efficiency is improved, but authentication and authorization control is weakened
Solution Approach 1:
The proxy service serves as a mediator that maintains authorization control while preserving communication efficiency. It validates authentication tokens and enforces authorization policies before allowing requests to pass through to the service provider. Once authorized, the proxy service forwards requests directly without interfering with the actual service communication, thus maintaining both control and efficiency.
Data Source
AI summary
A method for using a proxy service as an intermediary between an end service and a client for authenticating and authorizing software is provided. The method includes: receiving a first service request from a user; generating and transmitting a request for an identity authentication token by mapping information included in the first request to an application programming interface (API) that is used by an identity provider; receiving a second service request in conjunction with the identity authentication token; verifying an authorization of the user; generating and transmitting a third service request by mapping information included in the authorization of the user to an API that is used by a service provider; receiving data is responsive to the third service request from the service provider; and transmitting data that is responsive to the second service request to the user.