How it works
The Automatic Login Form and Recorded methods each run in two stages. The normal login runs first, and the AI agent only steps in if it fails.The normal login runs
For Automatic Login Form, the scanner finds the login form with pattern-based selectors. For Recorded, it replays the steps you recorded. Both handle standard logins well.
What AI handles
The AI component handles scenarios that the normal login methods struggle with:Dynamic forms
Login forms loaded via JavaScript or AJAX
Iframes
Login forms embedded in iframes
Non-standard layouts
Forms with unusual element structures or naming
Multi-step logins
Login flows spread across multiple screens
Reliability
AI-enhanced authentication raises login success rates on complex or dynamic pages, where selector matching or step replay would otherwise fail.Using AI authentication
Enabling automatic login form
The Recorded method uses the same AI fallback, with no extra setup. See Recorded authentication to set it up.
Generated finding
When automatic authentication succeeds, the scan generates an informational finding:Authentication complete: Automatic method.
Each authentication method generates its own confirmation message. For example, the Recorded method displays: “Authentication complete: Recorded method.”
When AI is used
The AI component activates only when needed:- Standard forms: Traditional detection handles most login forms without AI
- Complex forms: AI activates automatically when traditional detection fails
- Transparent operation: You don’t need to configure anything. The system chooses the best approach
The scan result shows the method you chose, for example “Authentication complete: Automatic method” or “Authentication complete: Recorded method”. It doesn’t indicate whether the AI fallback was used.
Other authentication methods
The AI fallback backs the Automatic Login Form and Recorded methods. The remaining methods work differently:| Method | How it works | Uses AI |
|---|---|---|
| Automatic Login Form | Detects and fills login form automatically | Yes (as fallback) |
| Recorded | Replays recorded login steps from Chrome DevTools | Yes (as fallback) |
| Cookie | Uses session cookies from an existing login | No |
| Header | Sends custom authentication headers | No |
For both Automatic Login Form and Recorded, the AI agent only runs if the normal login fails. Cookie and Header authentication never use AI.
AI data handling
Your authentication credentials are handled securely:- Azure OpenAI models: The AI agent uses Azure-hosted OpenAI models within our controlled infrastructure
- Secure processing: Credentials are processed within our isolated infrastructure
- No external training: Your data is not used to train any AI models
- No retention: Authentication data is not logged or retained after the scan completes