Battlefield Portal login broken
Battlefield Portal login broken by two separate faults (CORS preflight returns 464, and redirect_uri mismatch in viaAuthCode)
Summary
On https://portal.battlefield.com/bf2042/experience/mode/game-mode, all buttons except the header and footer are unresponsive and no content loads (gamemode selection, etc.). The Angular app logs EmptyError: no elements in sequence. There are two independent causes, and both must be fixed.
Issue 1: CORS preflight rejected by the load balancer (HTTP 464)
- Request: OPTIONS https://kingston-prod-wgw-envoy.ops.dice.se/web.authentication.Authentication/viaAuthCode
- Request headers include Origin: https://portal.battlefield.com, Access-Control-Request-Method: POST, Access-Control-Request-Headers: content-type,x-dice-tenancy,x-grpc-web,x-user-agent
- Response: HTTP 464, server: awselb/2.0, content-length: 0, no Access-Control-Allow-Origin header (date: Sat, 21 Nov 2026 13:34:17 GMT)
- Result: the browser blocks every call to this host (viaAuthCode, getScheduledBlueprints, getConstraints, getProgressionTypes, ...) with "No 'Access-Control-Allow-Origin' header is present".
- Note: 464 is the AWS ALB "incompatible protocol versions" error, so the preflight seems to be rejected by the load balancer or target group before it reaches Envoy. This is a hypothesis; I can only see the response.
Issue 2: redirect_uri differs between the authorize step and the token exchange
- Authorize step (to accounts.ea.com): redirect_uri=https://portal.battlefield.com/experience/mode/game-mode/
- Token exchange (viaAuthCode request body): https://portal.battlefield.com/bf2042/experience/mode/game-mode/
- Response to viaAuthCode once CORS is bypassed: HTTP 200, grpc-status: 16, grpc-message: Failed to authenticate via auth code: Auth failed: Status(400), error: invalid_grant: redirect_uri is invalid
- The two URIs differ by the /bf2042 path segment. OAuth requires an exact match, so the code exchange fails.
- The page I started from was https://portal.battlefield.com/bf2042/experience/mode/game-mode.
Verification
I used a local proxy that (a) answers the preflight with a 204 and CORS headers, and (b) rewrites the redirect_uri in the viaAuthCode body to match the authorize step (removing /bf2042). With both in place, login succeeds and the Portal works. So these are the only two faults I found.
Steps to reproduce
- Open https://portal.battlefield.com/bf2042/experience/mode/game-mode
- Open DevTools (Network and Console tabs) and reload
- Observe the 464 on the OPTIONS request, the CORS errors in the console, and no usable content on the page
Environment
- Edge 157 (Windows 11), also reproduced in Firefox and in incognito mode
- Reproduced on 2026-11-21
Expected: the preflight returns 2xx with CORS headers, and the redirect_uri is identical in the authorize and token exchange steps.
Actual: see above.