Re:Firefox rolls out Total Cookie Protection by default to m...
by moi2388 on Thursday August 29, 2024 @12:35PM
(#41392629)
The flow is supported by the first party, but the login goes through a third party gateway which sends a token to the callback uri.
I think the previous poster was responding to this:
“I'm not sure what people are doing now, because you can't retain state.”
They do OAuth.
Re:Firefox rolls out Total Cookie Protection by default to m...
by andrewmcwatters on Thursday August 29, 2024 @12:57PM
(#41392901)
That's not what I'm talking about. I'm talking about scenarios where the authentication flow is not explicitly supported by the first party. It just exists through an iframe.
There is no replacement. It's just not possible anymore. OAuth doesn't address this.
Re:Firefox rolls out Total Cookie Protection by default to m...
by immibis on Thursday August 29, 2024 @03:17PM
(#41394343)
Yes, that's right. You can't steal credentials from another site without their permission.
Re:Firefox rolls out Total Cookie Protection by default to m...
by andrewmcwatters on Thursday August 29, 2024 @03:52PM
(#41394642)
No... that's not how that mechanism was ever used. The authentication flow I'm describing was used by companies to embed login flows for functionality that was delivered by iframe as companion behavior next to the first-party site.
Re:Firefox rolls out Total Cookie Protection by default to m...
by moi2388 on Friday August 30, 2024 @02:11AM
(#41398108)
OAuth. If you take Google as example, You let them sign in with Google through OAuth and then query the user data through the APIs. On-behalf-of/authorization code grant flow.
You can’t do an iframe, but you can still get the data if it’s supported by their api and yours.
Which is the way it should be, imo.
I've only ever seen it for explicitly supported authentication flows by the first-party site.