API Security Ecosystem for Remote Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Entities face challenges in implementing secure communication and managing sensitive digital content with third parties outside their network, due to the complexity of cryptographic solutions and lack of user-friendly, workable, authenticated B2C and B2B communication capabilities.

Innovation Solution

A Platform and API Security Ecosystem that provides cryptographic tools and features such as cross-certification, digital transaction signing, two-factor authentication, and tunable security, allowing entities to securely communicate and share sensitive information with third parties through encrypted channels, using standards like AES 256 and optional protocols, while maintaining control over encryption keys.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cryptographic solutions are implemented for secure communication, then security is improved, but system complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a Platform Service as an intermediary that handles cryptographic operations. The API acts as a mediator between the user's application and the complex cryptographic infrastructure, abstracting away the complexity while maintaining security. The Platform Service manages key pairs, digital signatures, and encryption/decryption operations centrally, so individual applications don't need to implement their own cryptographic systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If cryptographic tools are provided for secure communication, then security is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements automatic key pair generation and management. When a user first accesses the service, the Platform Service automatically generates a public-private key pair for that user and stores it securely. Digital signatures and encryption are automatically applied to communications without requiring users to manually configure cryptographic parameters. The system self-manages the cryptographic lifecycle including key generation, storage, and usage.

Inventive Principle:
Principle #25Self-service

3Reliability

If tested cryptographic solutions are implemented, then reliability is improved, but development time increases

Engineering Contradiction:
ImprovereliabilityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The Platform Service provides a universal cryptographic infrastructure that serves multiple functions: digital signature generation, public key distribution, message encryption, and decryption. A single Platform Service instance can serve multiple applications and users simultaneously. The API provides standardized interfaces for these cryptographic operations, allowing developers to reuse the same infrastructure across different projects rather than implementing separate cryptographic systems for each application.

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

Data Source

PatentUS9843450B2System and method to use a cloud-based platform supported by an API to authenticate remote users and to provide PKI- and PMI- based distributed locking of content and distributed unlocking of protected content
Publication Date: 2017.12.12 T CENT
  • US9843450B2 patent drawing
  • US9843450B2 patent drawing
  • US9843450B2 patent drawing

AI summary

System and method for authenticating a computer user includes: sending an invitation message from an entity computer to an API for authenticating a user of a user computer; receiving and translating by the API the invitation message and sending the translated invitation message including the first public key to the platform server; sending an invitation response to the API to be translated and sending the translated invitation response to the entity computer; preparing a first message including a link and a unique code by the entity computer and sending the first message to the user computer; registering with the platform server utilizing the link and the unique code, and generating a second public key, by the user computer; receiving a correct answer to the secret from the user computer; receiving the second public key by the platform server; and authenticating the user based on the received correct answer.