[Bug]: Web Application Login Issue with Playwright

[satishkotapati]

Version

1.53.1

Steps to reproduce

Reaching out to see if we get any support or guidance on the playwright implementation ::

We are facing Issue in automating UI Web application Login with Playwright, as Playwright has restriction to capture browser pop up authentication, Programaticaly bypassing browser popup authentication- auth credentials sent but still it’s using windows login user.

Example :
Even if we pass test user(ABC) credentials, but it’s taking Local windows logged session user(XYZ) authentication, tried to open browser in incognito mode with Playwright script still observing same behavior from Playwright.

The data /Engs related test user ABC should be available on Dashboard screen, but we are seeing the Data/engs assigned to my User (XYZ) / Windows logged user on laptop/VM..

Please do let me know if any additional details needed related to this issue

Expected behavior

The data /Engs related test user ABC should be available on Dashboard screen, but we are seeing the Data/engs assigned to my User (XYZ) / Windows logged user on laptop/VM..

Actual behavior

The data /Engs related test user ABC should be available on Dashboard screen, but we are seeing the Data/engs assigned to my User (XYZ) / Windows logged user on laptop/VM..

Additional context

No response

Environment

System:
    OS: Windows 11 10.0.22631
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-1370P
    Memory: 16.29 GB / 31.59 GB
  Binaries:
    Node: 22.14.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.2 - C:\Program Files\nodejs\npm.CMD
  IDEs:
    VSCode: 1.101.1 - C:\Users\satishkotapati\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
  npmPackages:
    @playwright/test: ^1.53.1 => 1.53.1

[satishkotapati]

sample code

 page = await context.newPage();
    await test.step('KPI_HomePage', async () => {
    await page.goto('https://login.microsoftonline.com/GUID1/oauth2/v2.0/authorize?client_id=GUID2&response_type=id_token&redirect_uri=https://webAPP.com/APPportal/aad-sso-login-callback&response_mode=form_post&scope=openid%20profile&state=GUID3&nonce=GUID4&sso_reload=true', { timeout: 60000 });
    await expect(page.getByRole('heading', { name: 'Sign in' })).toBeVisible();
    await page.getByRole('textbox', { name: 'Sign in with your KPMG email' }).click();
    await page.getByRole('textbox', { name: 'Sign in with your KPMG email' }).fill('TestUserABC@domain.com');
    await page.getByRole('button', { name: 'Next' }).click();

[dgozman]

@satishkotapati Unfortunately, the repro script you provided does not work for me - there is no Sign in with your KPMG email in the page. We need a repro that we can run locally, otherwise we won't be able to help.

[pavelfeldman]

Please don't paste passwords for online services here.

[satishkotapati]

already .... Updated with generic string!!! saw it was deleted. Please suggest how to share the script ? shall i mock the user and password and repost the script?

[pavelfeldman]

https://github.com/microsoft/playwright/blob/main/FILING_ISSUES.md

[satishkotapati]

as discussed, uploading the sample project for review

Login_Issue.zip

[pavelfeldman]

I can see command line arguments passed to launch, we can't guarantee Playwright working when custom args are passed.

                '--auth-server-whitelist=_',
                '--auth-negotiate-delegate-whitelist=_',
                '--disable-blink-features=AutomationControlled'

I also am not sure I understand the issue as it still does not follow the template - no clear steps, no clear expectations, no minimal repro. I'll have to close it as non-actionable. If you believe there is a bug in Playwright, please follow the template.

[satishkotapati]

@pavelfeldman, this issue is not that code error. this is about the credentials which we pass to the script, as the explaination mentioned in the initial thread that ::

Scenario:: Windows logged in with UserA, but we are testing the application with testUser2@domain.com. So when the login to webapp is completed, we should see the data related to testUser, instead we are seeing the data related to UserA

Note: Still the above information need to be clarified or details needed plz let me know, am not sure what template is expected, we have filled all info and the script /repo for review.

[mxschmitt]

Could you try args: ['--auth-server-whitelist="_"'], instead? Chrome renamed it from whitelist to allowlist a few years ago. That might do what you want it to do and don't use the Windows auth.

See:

• https://stackoverflow.com/a/64675959/6512681
• https://stackoverflow.com/a/79258272/6512681