JMeter中使用WebDriver Sampler进行浏览器渲染测试时遭遇Windows Authentication弹窗问题求解决方案

Hey there, I’ve run into this exact issue before—Windows Auth popups are tricky because they’re system-level dialogs, not regular web elements that Selenium can target directly. Here are three solid approaches to get past them and keep your render time testing on track:

Approach 1: Embed Credentials in the URL (Quickest Fix) #

If your application supports it, this is the easiest way to bypass the popup entirely. Just append your username and password to the target URL in this format:

WDS.browser.get("http://yourUsername:yourPassword@your-app-domain.com/login");

Heads up: Some modern browsers (like Chrome 60+) block this method by default for security reasons. If that’s the case, move straight to the next approach.

Approach 2: Chrome-Specific Configuration #

If you’re using Chrome, you can tweak browser options to auto-handle the auth popup. Add these settings when initializing your ChromeDriver in the WebDriver Sampler:

// Set up ChromeOptions with auth whitelists for your domain
var chromeOptions = new org.openqa.selenium.chrome.ChromeOptions();
chromeOptions.addArguments("--auth-server-whitelist=your-app-domain.com");
chromeOptions.addArguments("--auth-negotiate-delegate-whitelist=your-app-domain.com");
chromeOptions.addArguments("--disable-features=OutOfBlinkCors");

// Disable browser password manager to avoid conflicts
chromeOptions.setCapability("credentials_enable_service", false);
chromeOptions.setCapability("profile.password_manager_enabled", false);

// Initialize the browser with these custom options
var driver = new org.openqa.selenium.chrome.ChromeDriver(chromeOptions);
WDS.browser = driver;

This tells Chrome to automatically use your system credentials (or you can configure specific ones via environment variables in some enterprise setups).

Approach 3: Simulate Keyboard Input with Java Robot Class #

If the above methods fail, this fallback uses Java’s Robot class to manually type credentials into the popup. Just make sure the popup has focus when the code runs:

// Wait for the popup to load (adjust the timeout based on your app's speed)
WDS.log.info("Waiting for Windows Auth popup...");
java.lang.Thread.sleep(2000);

// Initialize the Robot class
var robot = new java.awt.Robot();

// Helper function to type a full string without manually pressing each key
function typeString(robot, text) {
    for (var i = 0; i < text.length; i++) {
        var c = text.charAt(i);
        var keyCode = java.awt.event.KeyEvent.getExtendedKeyCodeForChar(c);
        robot.keyPress(keyCode);
        robot.keyRelease(keyCode);
        java.lang.Thread.sleep(100); // Small delay to ensure each key registers
    }
}

// Type username, tab to password field, type password, then press enter
typeString(robot, "yourUsername");
robot.keyPress(java.awt.event.KeyEvent.VK_TAB);
robot.keyRelease(java.awt.event.KeyEvent.VK_TAB);
typeString(robot, "yourPassword");
robot.keyPress(java.awt.event.KeyEvent.VK_ENTER);
robot.keyRelease(java.awt.event.KeyEvent.VK_ENTER);

Note: This method relies on the popup having focus, so it might not work in headless environments or if the test’s focus shifts unexpectedly. Use it as a last resort.

Start with Approach 1—it’s the least error-prone. If that’s blocked by your browser, try Approach 2. Only use Approach 3 if the first two don’t pan out.

内容的提问来源于stack exchange，提问作者Akshat