Member Avatar for rishabh95verma

I want to create a a application for my web page as seen on pageflakes.com by which a user can easily logon to his facebook account and see all his facebook information. A similar gadget can also be found on igoogle and you can add it from this URL http://www.google.com/ig/directory?type=gadgets&url=www.brianngo.net/ig/facebook.xml

Please guide. Its urgent

  • 4 Contributors
  • 4 Replies
  • 110 Views
  • 9 Months Discussion Span
  • Latest Post Latest Post by macneato

Dani AI

Generated

The original request from asked for a gadget that lets a user sign into Facebook and read their data. The secure, supported pattern is to register an app with Meta (Facebook) and use Facebook Login (OAuth 2) plus the Graph API to fetch user fields. Collecting raw credentials is unsafe; ’s caution about not asking for passwords is correct, and ’s point about stating required skills is relevant — useful skills are basic HTML/JS, an optional server-side endpoint, HTTPS, and an understanding of OAuth.

Implementation checklist (high level):

  • Register an app at Meta for Developers and configure platform + valid redirect URIs (Facebook Login).
  • Choose a flow: client-side (JS SDK / popup) for pure front-end gadgets, or server-side code to exchange a code for a token when the portal allows redirects.
  • Request only needed scopes; extended permissions require App Review.
  • Exchange the authorization code for an access token and call the Graph API for profile fields (Graph API).

Example URL patterns (replace placeholders with real values):

https://www.facebook.com/v{api-version}/dialog/oauth?
  client_id=APP_ID
  &redirect_uri=https://example.com/auth/callback
  &state=RANDOM
  &scope=public_profile,email
GET https://graph.facebook.com/me?fields=id,name,email&access_token=USER_ACCESS_TOKEN

Troubleshooting & cautions:

  • Use the state param to prevent CSRF and always serve redirects over HTTPS.
  • Many portal/iframe containers block third-party cookies and top-level redirects; prefer popup-based OAuth or a server proxy and communicate back via postMessage.
  • Exchange short-lived tokens for long-lived tokens when needed and never store secrets client-side.
  • Read the OAuth 2.0 primer for background (OAuth 2.0) and follow Meta’s docs for up-to-date details and permission review.

Recommended Answers

All 4 Replies

Member Avatar for rishabh95verma

Please reply fast, its urgent.

Member Avatar for peter_budo
  1. This is not 24/7 service just for you beside urgency to you does mean little to us. We have right to live too!
  2. You should know that there is this very important rule on the forum, read here
  3. In your urgent request you failed to tell us about your knowledge in this area and what are your skills
Member Avatar for josephajain

Thanks for this information.....

Member Avatar for macneato

Hi rishabh95verma,

haha got told off I see. Well it might be a little delayed but just for the sake of others, you would need to use facebooks API and develop a desktop application since i dont see many people giving their login details through your site.

Edited by macneato because: typo
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.