Server Access Token Management via File Manager Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In an environment where multiple applications run on the same terminal device, existing authentication methods require users to enter authentication information for each application separately, increasing user workload due to memory sharing restrictions and security concerns.

Innovation Solution

A server device that manages access tokens by storing them with expiration dates and terminal identification codes, allowing access tokens to be shared among applications while ensuring security, and postponing expiration dates for all tokens associated with a terminal device when a valid access token is used, thereby reducing the need for repeated user authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access tokens are stored in nonvolatile storage region reserved for each application, then security is improved, but user workload increases because users must enter authentication information for each application separately

Engineering Contradiction:
ImprovesecurityVSAvoiduser workload
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a file manager as an intermediary component that mediates between applications and the nonvolatile storage region. The file manager reads access tokens from the storage region and distributes them to applications that need them, allowing applications to share tokens without directly accessing the storage region. This resolves the contradiction by maintaining security (applications cannot directly write to storage) while enabling token sharing (file manager distributes tokens to multiple applications).

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The access token stored in the nonvolatile storage region serves multiple applications simultaneously through the file manager's distribution mechanism. Instead of requiring separate authentication for each application, a single stored token can be shared across multiple applications that the user has access rights for, reducing user workload while maintaining security through controlled access via the file manager.

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

2Reliability

If memory sharing among applications is restricted, then security is improved, but adaptability decreases because applications cannot share authentication information

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication sharing capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The file manager acts as an intermediary that enables authentication information sharing between applications without requiring direct memory access. Applications request tokens through the file manager, which retrieves them from the secure nonvolatile storage region and provides them to authorized applications. This maintains memory sharing restrictions for security while providing adaptability for authentication sharing through the mediator's controlled distribution.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the access token from the application-specific memory space and stores it in a separate, secure nonvolatile storage region managed by the file manager. This separation allows multiple applications to access the same token through the file manager without sharing memory spaces, thus maintaining security restrictions while enabling authentication sharing capability across applications.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If users enter authentication information for each application, then security is improved, but productivity decreases due to repeated authentication tasks

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary authentication by storing the access token in the nonvolatile storage region after the user's first authentication. Subsequent applications can retrieve this pre-stored token through the file manager without requiring the user to re-enter credentials. This preliminary action (storing the token) improves productivity by eliminating repeated authentication tasks while maintaining security through the controlled retrieval mechanism.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The file manager as an intermediary automates the token distribution process, eliminating the need for users to manually re-enter authentication information for each application. The file manager retrieves the stored token and provides it to applications automatically, improving authentication efficiency while maintaining security through controlled access. The user's productivity increases as the mediator handles the repetitive authentication task.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10650129B2Server device, service method, program, and non-transitory computer-readable information recording medium
Publication Date: 2020.05.12 RAKUTEN GROUP INC
  • US10650129B2 patent drawing
  • US10650129B2 patent drawing
  • US10650129B2 patent drawing

AI summary

A server device (100) receives access from an application (31) running on a terminal device (200). The server device (100) authenticates the application (31) of the terminal device (200) with a user name and a password and if successful, transmits an access token to the application (31) and approves access. Issuing an access token, the server device (100) postpones the expiration date given to other access tokens associated with the terminal device (200). When an access token received from the application (31) of the terminal device (200) is associated with the terminal device (200) and stored as being unexpired, the server device (100) approves access from the application (31) and postpones the expiration dates given to all access tokens associated with the terminal device (200).