It works for Facebook because Facebook is an OAuth2 provider and has specification support for the "scope" parameter. Therefore, Spring Social has built-in support for it and uses it if it's there.
It doesn't work for LinkedIn because LinkedIn is an OAuth 1 provider and its "scope" parameter is a LinkedIn extension to the spec. As it is now, Spring Social is not expecting a scope parameter for OAuth 1 providers, so it ignores it if given one.
That's the subject of the other thread (http://forum.springsource.org/showth...ing-user-email) where we're discussing adding that feature to Spring Social. May I suggest that we confine the discussion to that thread so that we don't get lost managing it in multiple threads?
Spring Social Project Lead