This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
Help me understand better what it is you're doing. What do you mean by "the url of the app"? What app? What URL?
If you're saying that triggering the Spring Social connection flow takes you to Facebook's login page, that may be perfectly normal. The first step in an OAuth 2 authorization flow is to redirect the application to the provider's (e.g., Facebook's) authorization page. If the user hasn't yet logged into Facebook, then the first thing they'll see is the Facebook login page. After logging in, they'll be shown Facebook's authorization page.
I see. So, what I missed is that this is a Facebook Canvas application. In that case, Spring Social's connection flow isn't required (although I do have an example that uses it, it's not really the right way to do things and I do intend to fix that).
The right thing to do is to pull the access token from the signed request that Facebook will POST to your application. This is the subject of https://jira.springsource.org/browse/SOCIALFB-65. I need to update that sample to use the signed request. As I do that, I may uncover some improvements to properly hand off the token to the connection framework to create connections...but at the moment, that is left up to you.
This is definitely on my TODO list. If you're interested you should watch that issue...and if you're inclined, then I welcome you to try to adapt the example and submit a pull request. Specifically, you're going to want to look to SignedRequestDecoder to help you get the access token and then hand it off to the connection repository to create a connection.