We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

Lax Cookie Not Sent in iFrame on 302 Redirection

brian.l.coker
brian.l.coker
more options

I’m building an Angular application that is using OAuth2 Auth Code w/PKCE. The app uses hidden iframes to silently renew access tokens. I found that when the OAuth2 authorization serve redirects the iFrame to {parent origin}/silent-refresh.html with a 302, Firefox does not send any cookies set with SameSite: Lax.

SameSite: None cookies are sent as expected.

I compared this with IE and Chrome and both of those browser send the Lax cookies on when redirecting due to a 302.

This problem seems to only occur when the iFrame is being redirected via 302 from a different origin. I.e requests from a basic iFrame to the parent page origin send Lax cookies with no problem.

Anyone experience this? Is this expected behavior for Firefox?

Firefox Version 68.8

I’m building an Angular application that is using OAuth2 Auth Code w/PKCE. The app uses hidden iframes to silently renew access tokens. I found that when the OAuth2 authorization serve redirects the iFrame to {parent origin}/silent-refresh.html with a 302, Firefox does not send any cookies set with SameSite: Lax. SameSite: None cookies are sent as expected. I compared this with IE and Chrome and both of those browser send the Lax cookies on when redirecting due to a 302. This problem seems to only occur when the iFrame is being redirected via 302 from a different origin. I.e requests from a basic iFrame to the parent page origin send Lax cookies with no problem. Anyone experience this? Is this expected behavior for Firefox? Firefox Version 68.8

Vsi odgovori (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Does this also happen in current Firefox releases (current is 78.0.1) ?

There were some changes in Firefox 69.

brian.l.coker
brian.l.coker Lastnik vprašanja
more options

I’m working on getting a new version. My corporate version of Firefox comes bundled with some MFA software. So it hasn’t been as easy as just downloading the latest and retesting.

brian.l.coker
brian.l.coker Lastnik vprašanja
more options

Okay I was able to test this with 78.0.1 (64-bit) and the behavior is the same.