OAuth 2 0 and OpenID Connect for Single Page Applications Philippe De Ryck

[@TheMediinaa]

I absolutely loved this presentation! It made so many things so much clearer. My friend and I are working on a SPA + REST API project, and we thought it was a good idea to add login with Google to it. I was aware of the OAuth2.0 and OpenID Connect specifications, and thought it was going to be easy, until I found myself in a situation I didn't even know had an official term to it - Backend For Frontend. Every tutorial on the internet shows how to add Google login to either a traditional application, where the backend returns plain HTML to the browser, or purely on a SPA frontend, like the theme of this talk. So I came here thinking the presentation would talk about my problem, whereas in reality, it talks about a purely frontend based application. Just to find out at the end, that what I'm trying to implement is indeed a backend for frontend.

[@yosafatc.saputra5844]

Thank you, it's very detailed.

[@heshamamer3737]

Thanks for such a lean explanation, I loved every moment of it, and I hope that you know that you made things a lot clearer for me

[@galilioXX]

What a great session!! Thanks a lot Philippe!

[@rapha5586]

Super clean and to the point. Thanks!

[@kpavankumar007]

wow ! such an amazing and simplified explanation .

[@vinaykasireddy]

Excellent and elegant explaination

[@waujito]

Thanks a lot for such a great explanation. It was extremly helpful for me! You described all my questions about authorization in SPA with microservices

[@venkatraohyd]

Nice and great explanation ❤

[@Sanjay-pu4sp]

Fantastic explanation. Massive thanks!

[@osematouati2430]

Thanks a lot, great explanation

[@hashamkhan7951]

❤

[@nhlm4257]

Any tips on videos on how to implement the BFF pattern? Preferably using Spring Boot.

[@skapator]

How would the bff handle multiple calls for tolken refresh? Senario is, frontend sends 3-4 requests to get data.

[@bruxelleskarim]

Goeimorgen Philippe, Do you still suggest using a BFF (Backend For Frontend) or Token Handler when the Authorization Code Flow with PKCE is employed for SPAs (Single Page Applications)?

[@SunilMishra-s3m]

Great Explanation!!

[@gustabart]

Great explanation, Thanks! I don't understand why using BFF is safer. An attacker could still steal the browser's cookies and compromise the system. That is, it indirectly continues to use the tokens.

[@officialJoldag]

I think, it's because you are able to set the cookie with httponly, so it is not accessible via scripts.

[@Timo-iu4uc]

@@officialJoldag That's true. But the malicious code could execute any request and it would work, because the session cookie is sent to the backend automatically, right?

[@shanescad2384]

Thanks for sharing! However do you have a tutorial which implements Backend For Frontend (BFF) framework with Authorization code with PKCE in addition to this tutorial? It is unsafe to store access token on browser.

[@alessandrolima4266]

amazing !

[@tombalabomba3084]

I don't agree with the conclusion of this talk. The whole point of BFF and http-only auth cookies is to prevent an attacker that has gained acces to execute js code through an xss attack, to steal the auth-token from your storage and thereby execute requests on your behalf. If an attacker has managed to sucessfully gain access, he can execute api calls directly from the clients browser with or without bff.

[@sumitjoshi_01]

Thanks for the great explanation. I just want to ask you one thing that how an Identity provider makes a POST request to frontend application in Step no 9 (authorization response), especially in SPA application? And if it is making post request to my server then how I will return to user browser? Please help me, I am trying to implement apple id SSO with openId connect.