I used both of them in the project 2 months ago, and they both work well together. Spring Social should not give you any problems, because you request information on other sites (providers) without processing any authentication that does not belong to you.
The only tricky part is if you want to be an oAuth / oAuth2 service provider (so that other websites can click / retrieve information from your website, you provide an API for the customer website). The documentation is confusing, but it affects a separate namespace configured in the Spring security file, coexisting without overlapping with the rest of the application namespaces (a few "http" elements in your XML, some of them may be protected by OpenID - since Facebook will protect the form for sending updates status from another site: "do you allow example.com to publish updates?", others are publicly available - as a login form used to protect the previous action).
laffuste
source share