Browser Auto-Login via Server Meta Tags

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing auto-login systems in web browsers only pre-fill usernames and passwords when a user navigates to a specific login page, requiring manual login when landing on a different secure page, which is inconvenient for users who have already entered their credentials.

Innovation Solution

A system that automatically logs a user into a website by storing and submitting login information, even when the user initially navigates to a non-login page, by using meta tags with login parameters and HTTP methods to redirect the user securely, and validates cookies for seamless access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If the browser uses existing auto-login solutions that pre-fill usernames and passwords on login pages, then the login process is automated on specific login pages, but users still have to manually click a login button and are redirected to login pages when landing on secure pages

Engineering Contradiction:
Improveauto login processVSAvoidmanual login requirement
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The server performs preliminary action by embedding a meta tag with login parameters (username, password, login URL, HTTP method) directly in the HTML response of the secure page. This pre-configured login information is prepared in advance, allowing the browser to automatically execute the login process without manual intervention when the page is loaded.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service automation where the browser automatically detects the meta tag, extracts login parameters, and executes the login process without user intervention. The browser service itself performs the login action by sending a request to the login URL with the embedded credentials, eliminating the need for manual button clicking.

Inventive Principle:
Principle #25Self-service

2Reliability

If the server redirects users to a login page when they land on a secure page, then access control is maintained, but the user experience is degraded by requiring manual login

Engineering Contradiction:
Improveaccess controlVSAvoiduser convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The server performs preliminary action by embedding a meta tag with login parameters (username, password, login URL, HTTP method) directly in the HTML response of the secure page. This pre-configured login information is prepared in advance, allowing the browser to automatically execute the login process without manual intervention when the page is loaded.

Inventive Principle:
Principle #10Preliminary action

3Extent of automation

If the browser stores login information locally, then auto-login capability is enabled, but the system complexity increases due to additional storage and retrieval mechanisms

Engineering Contradiction:
Improvelogin automationVSAvoidbrowser functionality
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system enables self-service automation where the browser automatically detects the meta tag, extracts login parameters, and executes the login process without user intervention. The browser service itself performs the login action by sending a request to the login URL with the embedded credentials, eliminating the need for manual button clicking.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10389698B1Technique for facilitating auto login to a website
Publication Date: 2019.08.20 INTUIT INC
  • US10389698B1 patent drawing
  • US10389698B1 patent drawing
  • US10389698B1 patent drawing

AI summary

A computer-implemented method for facilitating an auto login from a browser to a website is provided. The browser sends a first request on behalf of a user for a secure page to the server for the website. The server then returns a response to the first request which includes HTML and one or more meta tags comprising a URL for a login page. Additionally, the meta tags specify the parameters the login page requires. After confirming that a credential for the user is stored in the browser, the browser issues a second request to the server with the credential and the URL for the login page from the meta tag. Next, the server returns a response to the second request which includes a cookie. After receiving the cookie, the browser saves the cookie and then reloads the secure page using the saved cookie without requiring a manual login operation.