When connecting via Spring Social's ConnectController or ProviderSignInController, authorization from Facebook is received server-side, but that doesn't necessarily mean that any of Facebook's JS API on the client side has equal authorization. This prevents things such as the Like button to work seamlessly when the application was authorized server-side.
This new feature issue is to explore ways to somehow authorize the client-side JS API from Spring Social's server-side authorization.
One option here, although not necessarily seamless, is to simply have the client-side request authorization again, after the server-side has already been authorized. Some experimentation is required here, but I believe that this may pop up an authorization dialog very quickly before closing it again (since the app has already been authorized). Even if this works, the temporary flash of the dialog would not be ideal.