Just a heads up to any of you using Spring Social with an OAuth2 provider such as Facebook, Google, or (as of now) LinkedIn...
LinkedIn now supports OAuth 2 in addition to OAuth 1. So, I upgraded Spring Social LinkedIn to work with OAuth 2 instead of OAuth 1.0a. Along the way this meant supporting the state parameter (for protecting against CSRF).
If you're using Spring Social LinkedIn, I'd appreciate it if you'd try it with the latest snapshots and make sure it all still works as you'd expect.
Even if you're not using Spring Social LinkedIn, but you are using Spring Social with another OAuth 2 provider, I'd still appreciate it if you'd test with the latest snapshots to make sure that the code I added for supporting the 'state' parameter doesn't break anything. I tested it rather well for Facebook and LinkedIn, but would appreciate more testing regardless of the provider.
Let me know if you run into any troubles.
LinkedIn now supports OAuth 2 in addition to OAuth 1. So, I upgraded Spring Social LinkedIn to work with OAuth 2 instead of OAuth 1.0a. Along the way this meant supporting the state parameter (for protecting against CSRF).
If you're using Spring Social LinkedIn, I'd appreciate it if you'd try it with the latest snapshots and make sure it all still works as you'd expect.
Even if you're not using Spring Social LinkedIn, but you are using Spring Social with another OAuth 2 provider, I'd still appreciate it if you'd test with the latest snapshots to make sure that the code I added for supporting the 'state' parameter doesn't break anything. I tested it rather well for Facebook and LinkedIn, but would appreciate more testing regardless of the provider.
Let me know if you run into any troubles.