| tags | projects | |||
|---|---|---|---|---|
|
|
This guide walks you through the process of creating a simple web application that accesses Facebook data.
You’ll build a web application that accesses data from a Facebook user profile, as well as posts from that user’s Facebook feed.
+ - An application ID and secret obtained from registering an application with Facebook.
Before you can fetch a user’s data from Facebook, you must specify your application’s ID and secret by setting the spring.social.facebook.appId and spring.social.facebook.appSecret properties. You can set these via any means supported by Spring Boot, including setting them in an application.properties file:
src/main/resources/application.properties
link:complete/src/main/resources/application.properties[role=include]As shown here, the properties have fake values. The values given to these properties correspond to your application’s consumer key and secret you obtain when you register the application with Facebook. For the code to work, substitute the real values given to you by Facebook in place of the fake values.
The presence of these properties and Spring Social Facebook in the classpath will trigger automatic configuration of Spring Social’s ConnectController, FacebookConnectionFactory, and other components of Spring Social’s connection framework.
Although much of what ConnectController does involves redirecting to Facebook and handling a redirect from Facebook, it also shows connection status when a GET request to /connect is made. It defers to a view named connect/{providerId}Connect when no existing connection is available and to connect/{providerId}Connected when a connection exists for the provider. In this case, provider ID is "facebook".
ConnectController does not define its own connection views, so you need to create them. First, here’s a Thymeleaf view to be shown when no connection to Facebook exists:
src/main/resources/templates/connect/facebookConnect.html
link:complete/src/main/resources/templates/connect/facebookConnect.html[role=include]The form on this view will POST to /connect/facebook, which is handled by ConnectController and will kick off the OAuth authorization code flow.
Here’s the view to be displayed when a connection exists:
src/main/resources/templates/connect/facebookConnected.html
link:complete/src/main/resources/templates/connect/facebookConnected.html[role=include]With Facebook configured in your application, you now can write a Spring MVC controller that fetches data for the user who authorized the application and presents it in the browser. HelloController is just such a controller:
src/main/java/hello/HelloController.java
link:complete/src/main/java/hello/HelloController.java[role=include]HelloController is created by injecting a Facebook object into its constructor. The Facebook object is a reference to Spring Social’s Facebook API binding.
The helloFacebook() method is annotated with @RequestMapping to indicate that it should handle GET requests for the root path (/). The first thing the method does is check whether the user has authorized the application to access the user’s Facebook data. If not, the user is redirected to ConnectController with the option to kick off the authorization process.
If the user has authorized the application to access Facebook data, the application fetches the user’s profile as well as several of the most recent entries in the user’s feed. The data is placed into the model to be displayed by the view identified as "hello".
Speaking of the "hello" view, here it is as a Thymeleaf template:
src/main/resources/templates/hello.html
link:complete/src/main/resources/templates/hello.html[role=include]Although it is possible to package this service as a traditional web application archive or WAR file for deployment to an external application server, the simpler approach demonstrated below creates a standalone application. You package everything in a single, executable JAR file, driven by a good old Java main() method. And along the way, you use Spring’s support for embedding the Tomcat servlet container as the HTTP runtime, instead of deploying to an external instance.
src/main/java/hello/Application.java
link:complete/src/main/java/hello/Application.java[role=include]https://raw.githubusercontent.com/spring-guides/getting-started-macros/master/build_an_executable_jar_subhead.adoc https://raw.githubusercontent.com/spring-guides/getting-started-macros/master/build_an_executable_jar_with_both.adoc
... app starts up ...
Once the application starts up, point your web browser to http://localhost:8080. No connection is established yet, so this screen prompts you to connect with Facebook:
When you click the Connect to Facebook button, the browser is redirected to Facebook for authorization:
Click "Okay" to grant permission for the sample application to access your public profile and your feed.
Once permission is granted, Facebook redirects the browser back to the application. A connection is created and stored in the connection repository. You should see this page indicating that a connection was successful:
Click the link on the connection status page, and you are taken to the home page. This time, now that a connection has been created, you see your name on Facebook and a list of some recent entries in your home feed. Included for each post in the feed list is the name of the sender, the post’s message, and the post’s picture (if available).
Congratulations! You have developed a simple web application that obtains user authorization to fetch data from Facebook. The application connects the user to Facebook through Spring Social, retrieves data from the user’s Facebook profile, and also fetches profile data from the user’s Facebook friends.
The following guides may also be helpful:
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent