RPA Authentication Engine for Persistent Background Sessions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Robotic process automation (RPA) systems often experience runtime timeouts during sessions, leading to expired login credentials and interruptions in background operations, which can result in data loss and inefficient training of RPA bots.

Innovation Solution

An RPA authentication engine that iteratively interfaces with software applications using login credentials to persist sessions, employing cookie duration tracking and direct HTTP or webhook requests to maintain authentication status without user intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If RPA bots operate in background without continuous authentication, then ease of operation is improved, but reliability deteriorates due to runtime timeouts and expired login credentials

Engineering Contradiction:

Improvebackground operationVSAvoidauthentication persistence

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent implements continuous authentication by iteratively interfacing with the software application site using login credentials. The RPA authentication engine continuously maintains authentication status through repeated login attempts, ensuring the session remains active and preventing runtime timeouts. This continuous action resolves the contradiction by maintaining background operation capability while ensuring authentication persistence.

Inventive Principle:

Principle #20Continuity of useful action

Solution Approach 2:

The patent employs feedback mechanisms where the RPA authentication engine monitors authentication status and adjusts its behavior accordingly. When authentication expires or runtime timeouts occur, the system receives feedback and automatically re-authenticates using stored login credentials. This feedback loop ensures reliability is maintained while allowing uninterrupted background operations.

Inventive Principle:

Principle #23Feedback

2Reliability

If RPA bots continuously monitor and re-authenticate, then reliability is improved, but device complexity increases

Engineering Contradiction:

Improvesession persistenceVSAvoidauthentication engine complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The RPA authentication engine performs self-service by automatically managing its own authentication process. It stores login credentials, monitors authentication status, and executes re-authentication without external intervention. This self-service capability improves reliability through continuous authentication while minimizing the complexity increase by eliminating the need for complex external authentication management systems.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent implements preliminary action by pre-storing login credentials and preparing the authentication engine to automatically re-authenticate when needed. The system performs preliminary authentication setup and credential storage before runtime issues occur, allowing reliable session persistence without requiring complex real-time authentication decision-making during operation.

Inventive Principle:

Principle #10Preliminary action

3Device complexity

If RPA bots timeout during sessions, then device complexity is reduced, but loss of information occurs due to expired credentials and interrupted operations

Engineering Contradiction:

Improveauthentication managementVSAvoiddata loss from interrupted operations

Core Design Contradiction:

Device complexityVSLoss of information

Solution Approach 1:

The patent ensures continuity of useful action by implementing continuous authentication that prevents runtime timeouts. The RPA authentication engine iteratively interfaces with the software application site, maintaining an active authentication state throughout the bot's operation. This continuity prevents credential expiration and session interruptions, thereby eliminating data loss while keeping authentication management relatively simple.

Inventive Principle:

Principle #20Continuity of useful action

Solution Approach 2:

The patent applies beforehand cushioning by preparing authentication mechanisms in advance that prevent credential expiration and session timeouts before they can cause data loss. The system stores login credentials and maintains authentication state proactively, cushioning against the harmful effects of expiration and interruption. This proactive approach prevents information loss without requiring complex real-time protection systems.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS12418518B2Robotic process automation log-in method for authentication

Publication Date: 2025.09.16 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A method for persisting a robotic process automation (RPA) session receives, through an RPA authentication engine, a software application site being interacted with by an end user. The RPA authentication engine deploys a bot running the RPA session on the software application site. The RPA authentication engine identifies login credentials of the end user associated with the software application site. The RPA authentication engine receives confirmation of an initial login to the software application site by the end user. The RPA authentication engine iteratively interfaces with the software application site using the login credentials to persist the RPA session.