microsoft / microsoft/playwright-java
[Bug]: Edge channel browser process crashes/closes page context during cross-origin SAML/OIDC redirect in v1.62.0
Nessuno ha ancora preso questa issue.
- Lingua principale
- Java
- Stelle
- 1.6k
- Fork
- 298
- Merge medio
- 3g 2h
- PR unite (30g)
- 14
Descrizione
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
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia con la configurazione di avvio Java usando setChannel("msedge") e riproduci il flusso di reindirizzamento OIDC/SAML attraverso la schermata KMSI di Entra ID. Confronta Edge 1.62.0 con Chromium incluso, Chrome, Firefox e Playwright 1.59.0, usando il trace PageImpl.didClose come segnale del fallimento. Il lavoro è completato quando la pagina di Edge rimane aperta e raggiunge l’applicazione di destinazione dopo il reindirizzamento.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- testing-qa
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 42/100