microsoft / microsoft/playwright-java

[Bug]: Edge channel browser process crashes/closes page context during cross-origin SAML/OIDC redirect in v1.62.0

Ouverte
#1,963 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Langage dominant
Java
Étoiles
1.6k
Forks
298
Merge moyen
3 j 2 h
PR mergées (30 j)
14

Description

Version

1.62.0

Steps to reproduce
  1. Configure Playwright 1.62.0 in Java using the Microsoft Edge channel:
BrowserType.LaunchOptions launchOptions = new BrowserType.LaunchOptions()
        .setHeadless(false)
        .setChannel("msedge");
  1. Navigate to an enterprise application URL protected by an OIDC / SAML 2.0 gateway (IBM Security Access Manager integrated with Microsoft Entra ID / Azure AD).

  2. Fill in user credentials and submit the form.

  3. On the Entra ID "Keep Me Signed In" (KMSI) screen (login.microsoftonline.com/kmsi), click the final submit button (#idSIButton9).

  4. Observe the browser context behavior as Entra ID executes the top-level POST redirect back to the application's OIDC authorization endpoint (/oidc/endpoint/default/authorize).

Expected behavior

The Edge browser tab should process the top-level OIDC authorization redirect cleanly, remain open, and navigate to the target application URL.

Actual behavior

During the SAML/OIDC POST redirect handoff immediately following the KMSI submission, the active browser page target closes unexpectedly (PageImpl.didClose event fires). Any subsequent Playwright navigation waiter or frame listener fails immediately with:
com.microsoft.playwright.PlaywrightException: Target page, context or browser has been closed

Note: This failure is isolated strictly to the Edge channel binary on 1.62.0. Running the exact same test flow on 1.62.0 using bundled Chromium, Google Chrome (chrome), or Firefox (firefox) works as expected without closing the page target.

Additional context
  • Regression Window: Works cleanly in Playwright 1.59.0 (all channels). Fails in 1.62.0 when using setChannel("msedge").

  • Telemetry Observation: Console logs show Microsoft BSSO telemetry attempting native broker calls prior to the crash: BSSO Telemetry: {"result":"Error","error":"bssoNotSupported"... "window.navigator.msLaunchUri is not available"}.

Trace Snippet:

[WARN] Redirect to: https://login.microsoftonline.com/kmsi
[WARN] Redirect to: https://miloginwidev.michigan.gov/oidc/endpoint/default/authorize...
[WARN] Page closed from thread: main
    at com.microsoft.playwright.impl.PageImpl.didClose(PageImpl.java:255)
    at com.microsoft.playwright.impl.PageImpl.handleEvent(PageImpl.java:242)
    at com.microsoft.playwright.impl.Connection.dispatch(Connection.java:314)
    at com.microsoft.playwright.impl.FrameImpl.waitForURLImpl(FrameImpl.java:1044)
    at com.microsoft.playwright.impl.PageImpl.waitForURL(PageImpl.java:1647)
com.microsoft.playwright.PlaywrightException: Target page, context or browser has been closed
  • Due to state government security policies and internal network constraints, live test credentials and internal domain URLs cannot be publicly provided.
Environment
  • Playwright Version: 1.62.0
  • Operating System: Windows 11
  • Browser: Microsoft Edge (Channel: msedge) > playwright chromium v1234
  • Language/JDK: Java 17

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez avec la configuration de lancement Java en utilisant setChannel("msedge") et reproduisez le flux de redirection OIDC/SAML via l’écran KMSI de Entra ID. Comparez Edge 1.62.0 avec Chromium inclus, Chrome, Firefox et Playwright 1.59.0, en utilisant la trace PageImpl.didClose comme signal d’échec. C’est terminé lorsque la page Edge reste ouverte et atteint l’application cible après la redirection.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
java
Domaine
testing-qa
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Active
Clarté
Plutôt claire
Accessibilité débutants
42/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.