Hybrid App Authentication via Policy File Scope Tokens

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Hybrid mobile applications face challenges in authentication due to duplicated code and synchronization issues between web and native modules when interacting with backend servers, leading to a degraded user experience, such as requiring users to log in twice.

Innovation Solution

A method involving a key pair and policy file is used to authenticate mobile applications, generating scope tokens with multiple authentication scopes, which are then sent to a security gateway for user authentication, ultimately providing an access token for seamless interaction with backend services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate authentication processes are used for web and native modules, then each module can be authenticated independently, but users are required to log in twice resulting in degraded user experience

Engineering Contradiction:
Improveauthentication reliabilityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent combines separate authentication processes for web and native modules into a unified authentication flow. A single authentication request from the hybrid application triggers coordinated authentication of both modules, resulting in a shared session cookie that both modules can use. This eliminates the need for duplicate logins while maintaining authentication reliability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal authentication mechanism where a single authentication process serves multiple purposes: authenticating both web and native modules simultaneously, generating a session cookie that works for both interfaces, and providing a unified user experience across different application modules.

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

2Adaptability or versatility

If duplicated implementations of remote invocation modules are maintained for web and native interfaces, then both interfaces can interact with backend servers independently, but synchronization issues and increased maintenance complexity arise

Engineering Contradiction:
Improveinterface adaptabilityVSAvoidcode complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal authentication framework that works across both web and native interfaces through a common protocol. The authentication module serves multiple functions: handling authentication for web requests, handling authentication for native requests, and coordinating between the two interfaces using a shared session management system.

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

Solution Approach 2:

The patent introduces an intermediary authentication coordination mechanism that mediates between web and native modules. This intermediary layer manages session cookies and authentication states, allowing both interfaces to interact with the backend server independently while maintaining synchronization through the coordinating authentication module.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10277409B2Authenticating mobile applications using policy files
Publication Date: 2019.04.30 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10277409B2 patent drawing
  • US10277409B2 patent drawing
  • US10277409B2 patent drawing

AI summary

Examples of techniques for authenticating mobile applications are described herein. A method includes receiving, via a first server, a key pair and a policy file associated with a mobile service from a second server. Authentication of the mobile application is performed based on the key pair and the policy file. A scope token is generated with an application scope in response to authenticating the mobile application. Authentication of a client device is performed corresponding to the mobile application and a user to generate a doubly-authenticated scope token including a device scope and application authenticity scope. The doubly-authenticated scope token is sent to a security gateway for user authentication. A trebly-authenticated scope token is received with a grant token request and a grant token is sent to the mobile application. The grant token is received from the mobile application. An access token is generated and sent to the mobile application.