Session-Less Login for Multi-User Authentication Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user authentication protocols in applications with web views require users to log out and log in again when multiple users need to authenticate within the same session, disrupting ongoing workflows and sessions.
Innovation Solution
Implementing a session-less login process that allows multiple users to authenticate without establishing new sessions, using an identity provider system to verify credentials without creating new cookies, maintaining the original user's session intact.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional authentication protocol is used, then user authentication is secure, but multiple users cannot authenticate simultaneously in the same session
Solution Approach 1:
The authentication process is segmented into two independent parts: application-level session management and authentication-level session management. The application session cookie and authentication session cookie are separated, allowing multiple users to authenticate without affecting the application session. This segmentation enables a second user to authenticate while the first user remains logged in, resolving the contradiction between multi-user capability and session continuity.
Solution Approach 2:
The IdP authentication server acts as an intermediary that manages authentication sessions independently from application sessions. By introducing this intermediary layer, the system can establish authentication sessions for multiple users without creating conflicts in the application session, thus enabling simultaneous multi-user authentication while maintaining session reliability.
2Ease of operation
If session-based authentication is used, then user session is maintained, but second user cannot access first user's application session
Solution Approach 1:
The patent segments session management into application session (managed by application server) and authentication session (managed by IdP). The application session cookie remains with the first user while the IdP creates a separate authentication session for the second user. This allows the second user to authenticate and access the application without disrupting the first user's session, maintaining both session maintenance and multi-user access capabilities.
3Adaptability or versatility
If logging out first user enables second user authentication, then second user can access application, but application session is ended
Solution Approach 1:
By segmenting the session management into application-level and authentication-level, the system allows the second user to authenticate without logging out the first user. The application session continues uninterrupted while the IdP manages separate authentication sessions for each user, thus extending the application session duration while enabling second user authentication.
Solution Approach 2:
The IdP authentication server serves as an intermediary that handles second user authentication independently from the application session. This intermediary manages the authentication session separately, allowing the second user to join the application without terminating the first user's session, thereby maintaining application session duration while enabling multi-user access.
Data Source
AI summary
An agent computer system uses a session-less login process to log in two users in a same application session. The system establishes an application session with an application server and a user session with the application server by authenticating a first user using an identity provider system (IdP). The system detects a request to perform an action by the first user within the application session that requires a second user's authentication. While maintaining the user session, the system requests a session-less authentication of the second user by transmitting an authentication request, which includes a flag indicating that the requested authentication is a session-less authentication. The system receives a confirmation of the authentication of the second user without establishing a second user session and performs the requested action in response to receiving the confirmation of the authentication of the second user.


