Security Token Management Service in Application Server

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application server platforms require manual configuration and selection of token types and providers for user authentication and data access, which is cumbersome and inefficient.

Innovation Solution

A security token management service hosted in an application server that abstracts the management of token services and objects, allowing for automatic selection and deployment of token types and providers without manual configuration, integrating with various token services and providers to manage token-based security for applications and clients.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration of token types and providers is used, then system reliability is maintained through explicit control, but device complexity and administrative burden increase significantly

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The security token management service enables self-service configuration where the system automatically selects and configures token providers based on predefined policies and metadata, eliminating the need for manual administrator intervention in token configuration while maintaining system reliability through automated validation and selection mechanisms

Inventive Principle:
Principle #25Self-service

2Productivity

If manual selection and configuration of token providers is required, then configuration accuracy is ensured, but productivity and deployment speed are reduced

Engineering Contradiction:
ImproveproductivityVSAvoidconfiguration accuracy
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

Token provider configurations, metadata, and selection policies are predefined and prepared in advance within the security token management service. When a token is needed, the system automatically retrieves and applies the appropriate pre-configured settings, ensuring both rapid deployment and configuration accuracy without requiring manual selection at runtime

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system incorporates validation mechanisms that provide feedback on configuration correctness and token provider selection appropriateness. This feedback loop ensures that automated configurations meet required accuracy standards while maintaining high deployment speed through continuous verification

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If a unified security token service is implemented, then adaptability and versatility improve, but device complexity increases due to integration requirements

Engineering Contradiction:
ImproveadaptabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The security token management service provides universal functionality by supporting multiple token types and providers through a single unified interface. The service uses polymorphic design and metadata-driven architecture to handle diverse token requirements (SAML, OAuth, Kerberos, etc.) through the same service framework, enabling adaptability without requiring separate configuration mechanisms for each token type

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

Data Source

PatentUS9407626B2Security token management service hosting in application server
Publication Date: 2016.08.02 RED HAT INC
  • US9407626B2 patent drawing
  • US9407626B2 patent drawing
  • US9407626B2 patent drawing

AI summary

Systems and methods for a security token management service hosted in an application server. A set of services and/or associated applications can be served from an application server to one or more clients. The set of services may require one or more token services in order to deliver their intended functionalities, so that for instance an email client may require the use and presentation of a token or other object incorporating user ID, password, or other authentication information for the user to access and retrieve their email messages. Different served applications and/or services may require the installation of various different token types or services, conventionally requiring manually configuration. A centralized security token management service can be installed and configured in the application server itself, which interfaces to requesting services and automatically locates and acquires diverse token types and/or associated token services to support served applications or services.