Centralized Presentation Server for Consistent One-Time Password Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing identity verification methods for secured systems, such as one-time password (OTP) authentication, face challenges in providing a consistent user authentication experience across multiple web pages and applications while maintaining strong security and authentication capabilities, especially in environments where services are provided by different vendors.
Innovation Solution
Implementing a user interface widget that provides OTP functionality through a presentation server, utilizing security assertion markup language (SAML) for enhanced security, and allowing OTP input from tokens or mobile devices, ensuring a consistent user experience across various services by centralizing OTP functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If OTP functionality is implemented through multiple vendor services, then authentication capability is provided, but user experience consistency deteriorates
Solution Approach 1:
The patent introduces a presentation server as an intermediary layer between the user and multiple vendor services. This server receives requests from the user interface widget, determines the appropriate service provider, and redirects to the correct hosted page. The presentation server acts as a mediator that maintains consistent user experience while allowing multiple vendor services to operate independently in the background.
Solution Approach 2:
The system is divided into separate functional components: a user interface widget for consistent user interaction, a presentation server for logic and routing, and multiple vendor services for actual authentication. This segmentation allows each component to optimize its function independently while working together to provide both authentication capability and user experience consistency.
2Ease of operation
If centralized OTP functions are implemented, then user experience consistency is improved, but system complexity increases
Solution Approach 1:
The patent extracts the OTP functionality from individual vendor services and places it in a centralized presentation server. This extraction allows the complex authentication logic to be separated from the user interface, enabling consistent user experience while managing system complexity through modular architecture.
Solution Approach 2:
The presentation server is designed as a universal component that handles authentication requests from multiple vendor services through a single interface. This multi-functional approach consolidates complexity into one server while maintaining simple, consistent user interaction across all services.
3Reliability
If security authentication is enhanced, then security capability is improved, but implementation speed deteriorates
Solution Approach 1:
The patent implements preliminary action by pre-configuring the presentation server with authentication logic and vendor service connections before actual authentication events occur. The user interface widget is pre-programmed to interact with the presentation server in a standardized manner, enabling rapid deployment while maintaining strong security capabilities.
Solution Approach 2:
The system uses parameter changes to adapt to different security requirements. The presentation server can modify authentication parameters based on the specific vendor service and user needs, allowing enhanced security when required while maintaining fast implementation through configurable rather than hard-coded security measures.
Data Source
AI summary
Consistent one-time password (OTP) functionality is provided from a presentation server to secure various on-line resources. A seed file can be provided to or created by a service provider for execution as part of a hosted page displayed at a client to a user. A presentation server receives a call from the seed file. A user interface widget can be initialized at the presentation server in response to the call from the seed file. The widget can be displayed as part of the remotely hosted Web page so that the user perceives the UI widget to be embedded in the page as viewed on the client computer system. Security for the interaction between the servers can be provided through use of security assertion markup language (SAML).