Facebook Login Integration

Question

0

Facebook Login Integration

Richelle Onda posted 8 Years Ago

Hi Team,

I have been doing this Facebook login integration and yet it does not work.

I have managed to do Google and Twitter successfully but no luck with Facebook.

It seems I have configured everything correctly as there are no errors popping up.

What happens is when you click on the Facebook button, it will be authenticated by Facebook and be redirected to my RockRMS page but nothing happens.

I was not logged in whatsoever and just redirected to the login page where the Facebook button is.

Can you check it please. our external rockrms site is http://destinationcitychurch.org/page/207

May I know an answer for this please?

Nathan Parikh · Answer 1 · 2016-09-07T09:07-07:00

0

Nathan Parikh replied 8 Years Ago

Hi Richelle,

I had problems with it too initially, but the problem is likely with your Facebook app configuration.

One place to start would be to check the "Valid OAuth redirect URIs" under the Facebook Login Settings for your app.

~ Nathan

Jay Greentree · Answer 2 · 2016-09-07T12:25-07:00

0

Jay Greentree replied 8 Years Ago

Make sure your domain settings on the facebook developers page looks something like the image below with your rock urls

Richelle Onda · Answer 3 · 2016-09-14T06:28-07:00

0

Richelle Onda replied 8 Years Ago

I have tried these recommendations and even googled about possible solutions. Still, no luck :(

Knolly Shadrache · Answer 4 · 2018-08-08T03:00-07:00

0

Knolly Shadrache replied 6 Years Ago

I'm posting some of our experience on the road to getting facebook authentication working in the hope it will save time for someone.

Since May 2018, facebook started enforcing strict redirect urls. We had to do 2 things to get things working:

1. Enter the precise redirect URL - including the port address

We had to make sure the redirect URL was EXACT, and included the 'port' being used:

Eg

https://my.churchurl.org:443/page/207/ - The port in this case is :443

or http://my.churchurl.org:80/page/207/ - The port in this case is :80

You can test the redirect URL at the bottom of the app page in facebook developer.

2. Fix the broken return url

We found that after the user was authenticated, they were sent back to the internal Rock home page instead of the external page (we are using external for non staff). If someone isn't staff, they didn't have access so they got a permissions complaint notice page instead of getting into the site.

This happened because in facebook authentication, Rock looked for a parameter called 'returnurl' that is not permitted in the redirect url configured in the facebook app. So as it couldn't find the return url, it defaulted to whatever it found in web.config, which is the Internal site home page:

We changed this from "Page/12" to "Page/1" to fix this second issue.If there's a better way I guess someone can let us all know.

After these changes everything worked!!

Edit Answer

I'm posting some of our experience on the road to getting facebook authentication working in the hope it will save time for someone.Since May 2018, facebook started enforcing strict redirect urls. We had to do 2 things to get things working: 1. Enter the precise redirect URL - including the port address We had to make sure the redirect URL was EXACT, and included the 'port' being used:Eg https://my.churchurl.org:443/page/207/ - The port in this case is :443 or http://my.churchurl.org:80/page/207/ - The port in this case is :80 You can test the redirect URL at the bottom of the app page in facebook developer. 2. Fix the broken return url We found that after the user was authenticated, they were sent back to the internal Rock home page instead of the external page (we are using external for non staff). If someone isn't staff, they didn't have access so they got a permissions complaint notice page instead of getting into the site. This happened because in facebook authentication, Rock looked for a parameter called 'returnurl' that is not permitted in the redirect url configured in the facebook app. So as it couldn't find the return url, it defaulted to whatever it found in web.config, which is the Internal site home page:&nbsp;&nbsp; &lt;authentication mode="Forms"&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;forms cookieless="UseCookies" defaultUrl="Page/12" loginUrl="Login" name=".ROCK" slidingExpiration="true" timeout="15" /&gt; &nbsp;&nbsp;&nbsp; &lt;/authentication&gt; We changed this from "Page/12" to "Page/1" to fix this second issue.If there's a better way I guess someone can let us all know. After these changes everything worked!!

<p><p>I'm posting some of our experience on the road to getting facebook authentication working in the hope it will save time for someone.</p><p>Since May 2018, facebook started enforcing strict redirect urls. We had to do 2 things to get things working:</p><p><br></p><p><b>1. Enter the precise redirect URL - including the port address</b><br></p><p>We had to make sure the redirect URL was EXACT, and included the 'port' being used:</p><p>Eg<br></p>https://my.churchurl.org:443/page/207/ - The port in this case is :443<br></p><p><br></p><p>or http://my.churchurl.org:80/page/207/ - The port in this case is :80<br></p><p>You can test the redirect URL at the bottom of the app page in facebook developer.</p><p><br></p><p><b>2. Fix the broken return url</b><br></p><p>We found that after the user was authenticated, they were sent back to the internal Rock home page instead of the external page (we are using external for non staff). If someone isn't staff, they didn't have access so they got a permissions complaint notice page instead of getting into the site.<br></p><p><br>This happened because in facebook authentication, Rock looked for a parameter called 'returnurl' that is not permitted in the redirect url configured in the facebook app. So as it couldn't find the return url, it defaulted to whatever it found in web.config, which is the Internal site home page:</p><p>&nbsp;&nbsp; &lt;authentication mode="Forms"&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;forms cookieless="UseCookies" defaultUrl="<span style="background-color: rgb(255, 255, 0);">Page/12"</span> loginUrl="Login" name=".ROCK" slidingExpiration="true" timeout="15" /&gt;<br>&nbsp;&nbsp;&nbsp; &lt;/authentication&gt;<br></p><p><br></p><p>We changed this from "Page/12" to "Page/1" to fix this second issue.If there's a better way I guess someone can let us all know.<br></p><p><br></p><p>After these changes everything worked!!</p><p><br></p>

<p><p>I'm posting some of our experience on the road to getting facebook authentication working in the hope it will save time for someone.</p><p>Since May 2018, facebook started enforcing strict redirect urls. We had to do 2 things to get things working:</p><p><br></p><p><b>1. Enter the precise redirect URL - including the port address</b><br></p><p>We had to make sure the redirect URL was EXACT, and included the 'port' being used:</p><p>Eg<br></p>https://my.churchurl.org:443/page/207/ - The port in this case is :443<br></p><p><br></p><p>or http://my.churchurl.org:80/page/207/ - The port in this case is :80<br></p><p>You can test the redirect URL at the bottom of the app page in facebook developer.</p><p><br></p><p><b>2. Fix the broken return url</b><br></p><p>We found that after the user was authenticated, they were sent back to the internal Rock home page instead of the external page (we are using external for non staff). If someone isn't staff, they didn't have access so they got a permissions complaint notice page instead of getting into the site.<br></p><p><br>This happened because in facebook authentication, Rock looked for a parameter called 'returnurl' that is not permitted in the redirect url configured in the facebook app. So as it couldn't find the return url, it defaulted to whatever it found in web.config, which is the Internal site home page:</p><p>&nbsp;&nbsp; &lt;authentication mode="Forms"&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;forms cookieless="UseCookies" defaultUrl="<span style="background-color: rgb(255, 255, 0);">Page/12"</span> loginUrl="Login" name=".ROCK" slidingExpiration="true" timeout="15" /&gt;<br>&nbsp;&nbsp;&nbsp; &lt;/authentication&gt;<br></p><p><br></p><p>We changed this from "Page/12" to "Page/1" to fix this second issue.If there's a better way I guess someone can let us all know.<br></p><p><br></p><p>After these changes everything worked!!</p><p><br></p>

Save Cancel

Question

0

Facebook Login Integration

0

0

0

0