Front-End Application Decoupling for External Service Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional information processing apparatuses face a lack of versatility in their front-end application configurations due to the need for specific settings based on external service specifications, limiting their adaptability and convenience.
Innovation Solution
An information processing apparatus with a communication interface, processor, and memory that includes a front-end application with a UI and a back-end application without a UI, where the processor manages the authorization code flow with an external service, allowing the front-end application to redirect using a pre-associated URL and acquire an access token using the back-end application's information, thereby decoupling the front-end from specific external service configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the front-end application is configured with specific settings based on external service specifications, then the authorization code flow can be controlled properly, but the versatility and adaptability of the application is reduced
Solution Approach 1:
The application is divided into two distinct parts: a front-end application that handles user interface and authorization code flow control, and a back-end application that stores service-specific configuration information. This segmentation allows each component to have specialized functions without compromising the other's versatility.
Solution Approach 2:
The back-end application acts as an intermediary that stores and provides authorization code flow information to the front-end application. This mediator contains the service-specific configurations, allowing the front-end to operate with high versatility while maintaining reliable authorization control through the back-end's stored information.
2Ease of operation
If the front-end application has integrated control of authorization code flow and external services, then the application can function independently, but the configuration becomes complex and service-specific
Solution Approach 1:
The service-specific configuration information is extracted from the front-end application and stored in the back-end application. This extraction reduces the complexity of the front-end application, making it easier to operate while maintaining its ability to function independently through access to the back-end's stored information.
Solution Approach 2:
The front-end application is designed with universal functionality to work with multiple external services by accessing authorization code flow information from the back-end. This multi-functionality approach allows the front-end to operate independently across different services without requiring service-specific configuration integration.
3Extent of automation
If the built-in application integrates main functions, authorization code flow control, and external service control, then the application is self-sufficient, but it lacks versatility when dealing with multiple external services
Solution Approach 1:
The system transitions from a single-dimension integrated application to a two-dimensional architecture where the front-end application operates in one dimension (user interaction and authorization control) while the back-end application operates in another dimension (configuration storage and management). This dimensional separation enables self-sufficiency in the front-end while achieving multi-service versatility through the back-end's centralized configuration management.
Data Source
AI summary
An image forming apparatus includes a communication interface, a processor, and a memory. The communication interface communicates with an external service including an authorization code flow. The memory stores a front-end application having a UI and a back-end application having no UI and registered in the external service, which are programs executed by the processor. The processor causes the external service to execute the authorization code flow based on the information of the back-end application in response to a request from the front-end application, receives an authorization code from the external service, causes the front-end application to redirect using a URL previously associated with the back-end application on the external service, and acquires an access token from the external service by the back-end application using the authorization code.