RPA Bot Credential Management for Multi-Factor Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing robotic process automation (RPA) systems struggle to automate tasks involving applications that employ multi-factor authentication (MFA), as they require additional credentials beyond login identification and password.

Innovation Solution

The RPA system interacts with applications by retrieving and providing user credentials, including generating a one-time password using a security key stored in credential storage, or retrieving credentials via a secondary channel like email or SMS, to facilitate MFA authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If conventional RPA systems are used to automate tasks, then automation capability is provided, but they cannot handle applications requiring multi-factor authentication

Engineering Contradiction:
Improveautomation capabilityVSAvoidcompatibility with MFA applications
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary credential management system that acts as a mediator between the RPA bot and the MFA application. This intermediary stores and manages multiple types of credentials (passwords, security keys, recovery codes) and retrieves them in response to authentication challenges, enabling the bot to handle MFA without direct user intervention.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-storing various authentication credentials (passwords, security keys, recovery codes) in the credential management system before they are needed. When authentication is required, the bot can immediately retrieve these pre-prepared credentials without requiring user presence or manual input.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If MFA is enabled for security, then security is enhanced, but automation of tasks becomes difficult or impossible

Engineering Contradiction:
ImprovesecurityVSAvoidautomation capability
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The credential management system provides self-service functionality by automatically managing the authentication credentials. The system stores credentials securely, detects when authentication is needed, retrieves the appropriate credentials, and provides them to the bot without requiring user intervention, thus maintaining both security and automation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The credential management system serves as an intermediary that bridges the security requirements of MFA and the automation needs of the bot. It handles the complex credential retrieval process behind the scenes, allowing the bot to maintain simple automation logic while security requirements are satisfied through the intermediary's credential management capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Extent of automation

If users disable MFA to enable automation, then automation is achieved, but security is compromised

Engineering Contradiction:
Improveautomation capabilityVSAvoidsecurity
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The system creates copies of authentication credentials (passwords, security keys, recovery codes) and stores them securely in the credential management system. These credential copies enable the bot to authenticate without requiring the user to disable MFA, thus maintaining both security and automation capability simultaneously.

Inventive Principle:
Principle #26Copying

4Reliability

If additional credentials are required for MFA, then security is improved, but system complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidcredential management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the management of multiple credential types (passwords, security keys, recovery codes) into a single credential management system. This unified approach consolidates what would otherwise be separate, complex credential handling processes into one integrated system, reducing overall complexity while maintaining security.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The credential management system is designed with multi-functionality to handle various types of credentials (passwords, security keys, recovery codes, email/SMS codes) through a single unified interface. This universal approach allows the system to manage diverse credential types without requiring separate management mechanisms for each, thereby reducing complexity.

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

Data Source

PatentUS12292960B2Automation of workloads involving applications employing multi-factor authentication
Publication Date: 2025.05.06 AUTOMATION ANYWHERE INC
  • US12292960B2 patent drawing
  • US12292960B2 patent drawing
  • US12292960B2 patent drawing

AI summary

A robotic process automation (RPA) system provides bots that interact with and provide user credentials to applications, such as for multi-factor authentication (MFA). First user credentials associated with MFA are retrieved by the bots from credential storage. Second user credentials that correspond to questions posed to a user of an application are retrieved from credential storage. Second user credentials that correspond to a one-time password are generated by the RPA system. The second user credentials may also be generated by a third-party authentication service that provides the credentials via a secondary channel such as email or SMS, which are then retrieved for presentation to the application.