microsoft / microsoft/playwright-java
[Bug]: Edge channel browser process crashes/closes page context during cross-origin SAML/OIDC redirect in v1.62.0
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Java
- Sterne
- 1.6k
- Forks
- 298
- Ø Merge
- 3 T. 2 Std.
- Gemergte PRs (30 T.)
- 14
Beschreibung
Version
1.62.0
Steps to reproduce
- Configure Playwright 1.62.0 in Java using the Microsoft Edge channel:
BrowserType.LaunchOptions launchOptions = new BrowserType.LaunchOptions()
.setHeadless(false)
.setChannel("msedge");
-
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).
-
Fill in user credentials and submit the form.
-
On the Entra ID "Keep Me Signed In" (KMSI) screen (login.microsoftonline.com/kmsi), click the final submit button (#idSIButton9).
-
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
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit der Java-Startkonfiguration mit setChannel("msedge") und reproduziere den OIDC/SAML-Weiterleitungsablauf über den KMSI-Bildschirm von Entra ID. Vergleiche Edge 1.62.0 mit dem gebündelten Chromium, Chrome, Firefox und Playwright 1.59.0 und verwende den PageImpl.didClose-Trace als Fehlersignal. Die Aufgabe ist abgeschlossen, wenn die Edge-Seite geöffnet bleibt und nach der Weiterleitung die Zielanwendung erreicht.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- testing-qa
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 42/100