Hi,
I have come across an issue while integrating Facebook login with AEM.
I took reference from below link
https://docs.adobe.com/docs/en/cq/5-6-1/administering/social_communities/social_connect.html
Although everything is working fine but on welcome page it is not displaying the logged in user name the way it is working for Geometrixx Outdoors website.
Instead it is displaiying the ID only.
Any suggestions who have already worked on this integration? :)
Views
Replies
Total Likes
Jay Brown wrote...
JK Kendall wrote...
akshitaa82720401 wrote...
@JK
One update on the issue :
Found that it is working as expected with Facebook API v2.3 and below. The issue exists for latest Facebook API v2.5.
Below are some of the findings:
OAuth 2.0 implementation for facebook connect is done via provider api by Adobe
“FacebookProviderImpl” class is responsible for fetching and storing Facebook User details into AEM. However, this implementation is not able to fetch first_name, last_name and various other details from Facebook profile due to API changes.
Tested for Facebook API v2.0(working) and v2.5(not working)
-Akshita
Hi Akshita,
Your update is very much appreciated! I'll see about putting a note on our doc page.
- JK
Hi there. I am trying to look into fixing this; however, I have setup an AEM instance to test this, but I don't see the issue.
I registered with my FB account, and my full name appears in the masthead area of the geometrixx-outdoors site. Also, if I dig into my profile, I see both my first and last name.
Can you describe the scenario to allow me to reproduce what you're seeing.
Thanks in advance.
-Jay
Hi Jay
Thanks for looking into this issue.
Have you created an app id in developers.facebook.com?
-Akshita
Views
Replies
Total Likes
Hi, Akshita -- I did and also used the FB API tester to confirm that v2.0 through and including 2.5 return first_name and last_name (https://developers.facebook.com/tools/explorer). As you can see, the basic information (first_name and last_name) work fine.
Please let me know what you can about your scenario.
Thanks and regards
-Jau
Views
Replies
Total Likes
Jay Brown wrote...
Hi, Akshita -- I did and also used the FB API tester to confirm that v2.0 through and including 2.5 return first_name and last_name (https://developers.facebook.com/tools/explorer). As you can see, the basic information (first_name and last_name) work fine.
Please let me know what you can about your scenario.
Thanks and regards
-Jau
Hi Jay,
In Graph API explorer, user details are coming for all versions. But I am not sure why the details are not getting stored in AEM.
Have you tried logging into Geometrix Outdoor site with your facebook configuration?
-Akshita
Views
Replies
Total Likes
Hi Akshita, I sure did. That was the first thing that I did. Please provide any details you can as I'd like to help you solve your issue.
Thanks and regards
-Jay
Views
Replies
Total Likes
Jay Brown wrote...
Hi Akshita, I sure did. That was the first thing that I did. Please provide any details you can as I'd like to help you solve your issue.
Thanks and regards
-Jay
Thanks Jay!!
But, When I am logging through Geometrixx it is displaying id only. Not sure why :(
I thought it is because of API version but for you it is working fine.
Previously I have attached all the screenshot. Please check it once and let me know if I am doing it differently than yours.
-Akshita
Views
Replies
Total Likes
Hello,
Any solution to the problem?
I am also facing same issue with AEM6.1 and here is steps I have taken;
Hi,
Akshita wrote :
Found that it is working as expected with Facebook API v2.3 and below.
The issue exists for latest Facebook API v2.5.
Internally, we've been unable to reproduce the problem with Facebook API v2.5.
The current recommendation is to open a support ticket if you need v2.5.
- JK
UPDATE : upgrade to AEM 6.1 Communities FP4 to get support for Facebook API v2.5.
JK Kendall wrote...
Hi,
Akshita wrote :
Found that it is working as expected with Facebook API v2.3 and below.
The issue exists for latest Facebook API v2.5.
Internally, we've been unable to reproduce the problem with Facebook API v2.5.
The current recommendation is to open a support ticket if you need v2.5.
- JK
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies