mTLS client certificate with XLT, Selenium, Chrome and Azure DevOps

[PetraH23]

Hi,

we are currently using XLT for browser-based test automation with Selenium and Chrome in an Azure DevOps CI environment.

We would like to automate the handling of an mTLS client certificate so that our test cases can run without any manual certificate selection during execution.

Based on your documentation, we understand that the XLT mTLS configuration via KeyStore and TrustStore applies to the underlying HtmlUnit WebClient. Our question is whether this support also applies to browser-based execution with Selenium and Chrome (webdriver.Chrome).

In our current setup, the Chrome options and arguments we provide seem to be applied only during package download, but not during the actual test execution. At runtime, the relevant settings appear to be controlled only via the browser settings. Modifying the Chrome profile directly on the machine is unfortunately not a viable option in our environment due to limited permissions and missing tools.

We would therefore appreciate your guidance on the following points:

• Does XLT support mTLS client certificates for browser-based execution with Selenium and Chrome?
• Is it possible to attach or provide a client certificate directly in the Selenium code for webdriver.Chrome or the Chrome session?
• Is this behavior known to you?
• Do you recommend any supported solution or workaround for this scenario in Azure DevOps?

Thank you very much for your support.

Kind regards,

Petra

[rschwietzke]

This is not really an XLT question; this is a ChromeDriver and Selenium question. This might help: https://share.google/aimode/wVDoPeAjT15dKaJzm

But it requires that you manage the ChromeDriver yourself. See below. Please let us know if this goes in the right direction.

Important: This code has not been tested recently. Your mileage might vary but might give you a hint.

public abstract class AbstractDesktop extends AbstractTestCase
{
    private static DesiredCapabilities capabilities;
    static
    {
        System.setProperty(ChromeDriverService.CHROME_DRIVER_EXE_PROPERTY,
                        XltProperties.getInstance().getProperty("xlt.webDriver.chrome_clientperformance.pathToDriverServer"));

        final ChromeOptions chromeOpts = new ChromeOptions();
        // chromeOpts.addArguments("user-agent="
        // + XltProperties.getInstance().getProperty("xlt.webDriver.chrome_clientperformance.userAgent.desktop"));

        capabilities = DesiredCapabilities.chrome();
        capabilities.setCapability(ChromeOptions.CAPABILITY, chromeOpts);
    }

    @SuppressWarnings("deprecation")
    public AbstractDesktop()
    {
        super(new XltChromeDriver(capabilities,
                        XltProperties.getInstance().getProperty("xlt.webDriver.chrome_clientperformance.screenless", true)));
        final WebDriver c = getWebDriver();
        c.manage().window().setSize(new Dimension(1400, 1000));
    }

    @After
    public void closeDriver()
    {
        getWebDriver().quit();
    }

}

P.S: We don't guarantee support using this channel. This is all just best effort when times permit. If you need guaranteed response time and a validated possible solution, please consider subscribing to XLT support.

[rschwietzke]

Hi @PetraH23, any news or udpates?