Centralized Authentication Server for Multi-Client UI Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Web application hosts face inefficiencies in updating and managing authentication processes across multiple clients, as each client must be individually updated to comply with security changes, leading to a duplicative and time-consuming process.

Innovation Solution

A central location server maintains the functionality of user interfaces for multiple clients, using a content scheduling engine to customize and serve context-specific content, allowing for centralized management of services while enabling unique branding and design for each client.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each client maintains its own authentication screen functionality to present unique branded content, then user interface customization and branding are improved, but the complexity and time required to update security features across all clients increases

Engineering Contradiction:
Improveuser interface customizationVSAvoidupdate complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system divides the authentication screen into two segments: a common functional framework maintained centrally and client-specific content displayed locally. This allows security updates to be applied once at the central level while clients maintain their unique branding through separate content layers.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The central authentication server provides a universal authentication framework that serves multiple clients simultaneously. This single framework handles authentication functionality for all clients, eliminating the need for each client to maintain separate authentication logic while still allowing customized content presentation.

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

2Reliability

If each client individually updates its authentication process to comply with security requirements, then security compliance is improved, but the time and resources required for updates increases

Engineering Contradiction:
Improvesecurity complianceVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system merges the authentication functionality into a single centralized server that handles all clients. Security updates are applied once to the central framework, and the changes automatically propagate to all clients, eliminating the need for individual client updates and significantly reducing update time.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The central authentication server acts as an intermediary between security requirement changes and individual clients. It receives security updates and translates them into actionable changes for all clients simultaneously, serving as a mediator that eliminates direct client-to-client update requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If clients maintain separate authentication functionality to ensure unique branding, then user experience and branding are improved, but the duplication of functionality across clients increases

Engineering Contradiction:
Improveuser experienceVSAvoidfunctionality duplication
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The authentication system is segmented into a common functional core and client-specific content layers. The functional core includes authentication logic, security features, and common UI elements that are shared across all clients. Client-specific branding and content are separated as distinct layers that can be customized without duplicating core functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A universal authentication framework is implemented that serves all clients through a single codebase. This framework provides the common authentication functionality once, and clients access it through standardized interfaces, eliminating redundancy while still allowing each client to present its unique brand identity through content customization.

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

Data Source

PatentUS9998452B1Customizing user interfaces for multiple different clients
Publication Date: 2018.06.12 AMAZON TECH INC
  • US9998452B1 patent drawing
  • US9998452B1 patent drawing
  • US9998452B1 patent drawing

AI summary

Techniques described herein provide customized user interfaces to users of clients based on the context of the client. For instance, the techniques may receive parameters that relate to specific client contexts, may transmit the parameters to a content scheduler, and may receive a schedule for serving context-specific user interface to the users. In response to receiving the content schedule, the techniques serve the context-specific content in scheduled locations of the customized user interface to the user.