The discussion revolves around enabling Facebook and Google OAuth to work within an iframe in Discourse. EGreg explains that OAuth fails due to X-Frame-Options restrictions and wants to use window.open() to handle authentication in a new window, then redirect back. merefield notes that running Discourse in an iframe isn’t officially supported, though a config variable exists to allow it, as seen in qbix.com and intercoin.app. EGreg clarifies the need to locate the JavaScript code responsible for the OAuth redirect (currently window.location.href = ...) to override it with window.open()—ideally via site theme JS without a plugin EGreg.
We are hosting Discourse in an iframe, so google oAuth doesn’t really work because they have x-frame options to prevent loading it.
What we’d like to do is use window.open and have the “small” oauth url for fb and google open up, and then upon closing redirect window.opener properly. Is this possible with Discourse settings? Or where is the code to do the location redirect, so we could change it?
I don’t believe this is officially supported. Discourse is a Single Page Application and there are no guarantees when it comes to running within an iframe.
Yup! So really my main question is — where is the code that is triggered when someone clicks Connect with Facebook or Google? How can I override it? Maybe in the site theme JS, so I don’t have to develop a plugin?
All I want to do is replace window.location.href = … with window.open()