The discussion revolves around a 403 error encountered when trying to log in to a Discourse forum using a Facebook app. cmdntd uses a WordPress plugin to enable Discourse login, but the error occurs due to Google’s OAuth2 policy, which blocks logins from embedded browsers like Facebook’s.
angus explains that the issue is not specific to Discourse or WordPress, but rather a result of Google’s restrictions. He suggests using a normal web browser instead of Facebook’s embedded browser or allowing alternative login methods.
cmdntd asks if Google might fix the issue in the future, and angus replies that it’s unlikely, as Google considers it a Facebook issue.
cmdntd proposes creating an option to redirect users to a different URL when encountering the 403 error, which angus doubts is possible due to the nature of the issue.
angus also suggests disabling the “auth immediately” and “login required” site settings, allowing guests to view the site without logging in. cmdntd explains that this is not feasible due to B2B requirements and local market demands.
The discussion concludes with cmdntd asking if it’s possible to prevent the forum from displaying before the login window appears, as customers are getting confused and trying to click on the forum instead of waiting for the login window.
Is anybody here?
This error is very important for my facebook customer now.
Hey there 
Sometimes you’ll find a slight delay in response when posting a support question late on Friday.
Your issue is not a WP Discourse, or a Discourse, one. It’s an issue caused by the fact that Google doesn’t allow OAuth2 logins in embedded browsers (e.g. Facebook’s embedded browser). You’ll find that a number of other websites have the same issue. For technical detail on the issue see here.
The solution is to use a normal web browser, instead of facebook’s web browser to use your Discourse instance, or perhaps allow for other login methods if you want to let your users use facebook’s web browser.
Thank you,
Well, it seems not able to help fb user.
Some local facebook users are most. But because I serve for B2B, gmail from G login is very important to contact…
Is there any chance for google fix this issue in the future?
Hi,
I have this idea,
Could you create an option to redirect to other URL when we have this 403?
This help we have more flexible to help user by some instruction
From Google’s perspective, it’s a Facebook issue 
This is not a Wordpress-specific question, so someone from the Discourse team might be more qualified to respond on this, but given that this is an issue between two different services unconnected with Discourse (Facebook and Google), I suspect there is not alot Discourse can do. Keep in mind this issue affects many services using Google login when sharing content on Facebook. This is not specific to Discourse.
I’m curious, if this is a B2B case that requires you only use google login, where does the need arise to support a large number of users clicking through from Facebook? In most B2B contexts, users are not interacting with a forum through a Facebook share.
Moreover, the issue seems to arise from the fact that people are being auto-redirected to google login on clicking a link to your site. Another solution here is to let guests view the site without logging in, i.e. disable the auth immediately and / or the login required site settings.
If you’re sharing content on facebook, requiring login to view content is a somewhat odd move, on top of the B2B context?
There are some conficts in using app in B2B here,
Facebook is not secure and there is not enough authentication for B2B. But because of custom in local or market demand, most of facebook users will force companies to keep using fb.
These aspects in market and technology make me have this issue.
A link without login is very appropriate. But there are 2 links in recommendation make users be confused than only one for login. So I wonder how to redirect to other link in 403 to keep first recommend link be only.
I suggest you just use one link, the link that doesn’t require the user to login. I wish I could help you further, but this is no longer a Discourse support question, it’s a question of how you’re designing your business workflows.
Hi,
When I use discourse wordpress plugin to login, it redirect to discourse and display forum first. This make customers misunderstood, and they try to click to forum, instead of wait for login window.
Could you make forum not to display before login window?
