Push Notification Authentication Server Load Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional push notification authentication methods for accessing restricted resources are inefficient due to polling mechanisms that cause server load and resource consumption, especially when handling multiple simultaneous requests, and can lead to timeouts and proxy issues.
Innovation Solution
A method that involves sending a first push notification to a user's device for authentication and a second push notification with the status of the authorization request, eliminating the need for continuous polling by the application, thereby reducing server load and improving resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the browser keeps polling for the status of the authentication request, then the authentication status can be continuously checked, but the server load increases and system resources are consumed
Solution Approach 1:
Instead of the browser actively polling the server for authentication status (client-initiated), the server pushes the authentication status to the browser via push notification (server-initiated). This inversion of the communication direction eliminates the need for continuous polling requests from the client, thereby reducing server load while maintaining reliable status checking.
2Adaptability or versatility
If multiple simultaneous authentication requests are handled, then user concurrency is supported, but the server becomes overwhelmed with polling requests
Solution Approach 1:
The push notification service acts as an intermediary between the server and the browser. When multiple authentication requests are handled simultaneously, the server sends notifications through this intermediary mechanism rather than relying on multiple client polling requests. This mediator approach allows the server to efficiently manage concurrent requests without being overwhelmed by repeated polling traffic.
3Ease of operation
If push notification authentication is implemented, then password management is eliminated and user experience is improved, but continuous polling is required which causes timeout and proxy issues
Solution Approach 1:
The system establishes a push notification subscription beforehand, creating a reliable communication channel before authentication is needed. This preliminary setup ensures that when authentication status needs to be communicated, the channel is already established and ready, avoiding timeout and proxy issues that would occur with ad-hoc polling requests.
Data Source
AI summary
The present disclosure relates to techniques for authentication of a user on a restricted website, or on an enterprise network with single sign-on, or on various other service systems with security restrictions using push notifications. One technique includes receiving an authorization request for a first application to access a resource, sending a first push notification to a second application, the first push notification requesting authentication of a user of the first application, receiving information indicating a response to the first push notification, sending a second push notification to the first application, the second push notification includes a status of the authorization request based on the response to the first push notification, receiving information indicating an outcome of the authentication request based on the response to the first push notification, and providing the first application access to the resource.