Error authenticating to IdP.: could not install driver: could not install driver: error: got non 200 status code: 403 (403 Forbidden - unexpected URL format) from https://playwright.download.prss.microsoft.com/builds/driver/playwright-1.47.2-linux.zip

[frreiro]

Description

The SAML2AWS Login returns error to install playwright driver.
When access the playwright download URL returns 403.

Details:

Ubuntu: 24.04.4 LTS
saml2aws: 2.36.19

Stack Trace

could not install driver: could not install driver: error: got non 200 status code: 404 (404 Not Found) from https://playwright.download.prss.microsoft.com/builds/driver/playwright-1.47.2-linux.zip
Error authenticating to IdP.
github.com/versent/saml2aws/v2/cmd/saml2aws/commands.Login
	github.com/versent/saml2aws/v2/cmd/saml2aws/commands/login.go:108
main.main
	github.com/versent/saml2aws/v2/cmd/saml2aws/main.go:199
runtime.main
	runtime/proc.go:283
runtime.goexit
	runtime/asm_amd64.s:1700

~/.saml2aws

Was follow the instructions on README.md file to install the browser driver by using download_browser_driver = true on .saml2aws config file. The config file looks like below:

[placeholder]
name                    = placeholder
app_id                  = {APP_ID}
url                     = {APP_URL}
username                = {USERNAME}
provider                = Browser
mfa                     = Auto
aws_urn                 = urn:amazon:webservices
aws_session_duration    = 3600
aws_profile             = {AWS_PROFILE}
role_arn                = {AWS_ROLE_ARN}
region                  = us-east-1
saml_cache              = false
download_browser_driver = true

[erpel]

The messages published in google-antigravity/antigravity-cli#566 suggest that it's a change in the way playwright assets are distributed by microsoft.

Microsoft has retired driver-zip distribution on all CDN endpoints (verified 2026-07-08):

So every playwright-go release before v0.6100.0 can no longer bootstrap the driver on a fresh machine.

Seems like the playwright-go package needs to be updated.

[gozeloglu]

The same problem happened to me.

[leonidasKap]

A workaround we are trying is this

go run github.com/playwright-community/playwright-go/cmd/playwright@v0.4702.0 install --with-deps chromium

the version v0.4702.0 comes from

curl -s https://raw.githubusercontent.com/Versent/saml2aws/v2.36.19/go.mod | grep playwright-go

This single command:

• Downloads the playwright-go driver to ~/Library/Caches/ms-playwright-go/1.47.2/node
• Downloads Chromium to ~/Library/Caches/ms-playwright/chromium-1134

[ianespana]

Unfortunately that workaround does not work. playwright-go still attempts to download the zip files from the same URLs, which are now invalid

$ go run github.com/playwright-community/playwright-go/cmd/playwright@v0.4702.0 install --with-deps chromium
go: downloading github.com/playwright-community/playwright-go v0.4702.0
go: downloading github.com/go-stack/stack v1.8.1
go: downloading golang.org/x/exp v0.0.0-20240506185415-9bf2ced13842
go: downloading github.com/go-jose/go-jose/v3 v3.0.3
go: downloading github.com/deckarep/golang-set/v2 v2.6.0
2026/07/09 10:58:26 could not download driver: error: got non 200 status code: 404 (404 Not Found) from https://playwright.azureedge.net/builds/driver/playwright-1.47.2-mac-arm64.zip
error: got non 200 status code: 404 (404 Not Found) from https://playwright-akamai.azureedge.net/builds/driver/playwright-1.47.2-mac-arm64.zip
error: got non 200 status code: 404 (404 Not Found) from https://playwright-verizon.azureedge.net/builds/driver/playwright-1.47.2-mac-arm64.zip
exit status 1

[danilodeLuca]

Opened a PR fixing it, hoping some main contributor could take a look in to it

#1532

[danilodeLuca]

Until its not solved, and if you have a colleague you trust, you can always go back to the 2000s and share a ZIP file by email or on a USB drive with the built ms-playwright-go folder

[rlevytskyi]

I have 404, too.
Error authenticating to IdP.: could not install driver: could not install driver: error: got non 200 status code: 404 (404 Not Found) from https://playwright.azureedge.net/builds/driver/playwright-1.47.2-linux.zip

@danilodeLuca colleague sent me the zip of his '~/.cache/ms-playwright-go/1.47.2/' folder but there is no clue how to 'install' it.

[ianespana]

colleague sent me the zip of his '~/.cache/ms-playwright-go/1.47.2/' folder but there is no clue how to 'install' it.

@rlevytskyi you just have to put it in the same folder as you mentioned. Note that it changes from OS to OS

[erpel]

I verified the #1532 locally which looks quite similar to #1535 - now all we need is a maintainer to take a look at either of them and decide if bumping the dependency can be released as a fix.

[steven130169]

Also reproducible on macOS (Apple Silicon) with Homebrew saml2aws v2.36.19.

saml2aws login --force --skip-prompt --role <role>
Error authenticating to IdP.: could not install driver
... playwright-1.47.2-mac-arm64.zip

All legacy driver mirrors return HTTP 404 for this artifact:

https://playwright.azureedge.net/builds/driver/playwright-1.47.2-mac-arm64.zip
https://playwright-akamai.azureedge.net/builds/driver/playwright-1.47.2-mac-arm64.zip
https://playwright-verizon.azureedge.net/builds/driver/playwright-1.47.2-mac-arm64.zip

Using an installed Chrome executable path and passing --no-download-browser-driver did not bypass the failure: saml2aws still attempts driver installation before the browser launches. This appears to affect the pinned playwright-go v0.4702.0 / Playwright 1.47.2 dependency rather than a specific browser or platform.

[chogyejin]

In my case (macOS Apple Silicon, Homebrew saml2aws v2.36.19) I got it working like this.

1.47.2 (the version my saml2aws pins) is 404 on the CDN, but 1.50.1 was still up — so I dropped that into the folder saml2aws looks in and just faked the version string:

CACHE=~/Library/Caches/ms-playwright-go/1.47.2
curl -sL -o /tmp/pw.zip "https://cdn.playwright.dev/dbazure/download/playwright/builds/driver/playwright-1.50.1-mac-arm64.zip"
mkdir -p "$CACHE" && unzip -oq /tmp/pw.zip -d "$CACHE" && chmod +x "$CACHE/node"
sed -i '' 's/"version": "1.50.1"/"version": "1.47.2"/' "$CACHE/package/package.json"
"$CACHE/node" "$CACHE/package/cli.js" install chromium
saml2aws login -a <account>

The driver is actually 1.50.1, but it only drives the IdP login browser, so the version gap didn't matter — login worked right after.

Notes: adjust the path/arch for your OS (~/.cache/... + linux on Linux, sed -i without '' on GNU). And 1.50.1 just happened to be the one version still on the CDN when I checked — if it 404s for you too, swap in whatever version still returns 200.