8 sept 2011 the Spring Social team proudly posted a post announcing Spring Social 1.0 under the title "What a year makes".
Indeed, a lot had been accomplished by providing a library that abstracts much of the complexities of oauth integration. As a result a pletora of implementations appeared both Spring and community lead.
There were some nagging issues that we started running into though. Speaking from my personal point of view:
* Dealing with errors in the oauth integration and automatically initiating new oauth flows when needed wasn't available leading to all sorts of issues especially in connecting based on stored connections and requiring some ugly hacks
* No support for refresh tokens leading to complexities in the Google oauth library
* Some providers such as Facebook changed their implementations along the way which required updates to the library
Well, more than a year later, I have to say I'm disappointed in the progress. It looked like after the 1.0.x releases, the team didn't get time allocated for this library anymore and the nags weren't addressed in a timely fashion. We now missed the 1.1.0M1 release target and there seem to be a lot of issues outstanding on that one, in particular the ones that cause me the most problems in using Spring Social.
This is open source so we have to rely on the efforts of the team and the community and therefore can't "complain". I do want to voice my concern on this though. The project is not getting the love it needs.
Kind regards,
Marc
Indeed, a lot had been accomplished by providing a library that abstracts much of the complexities of oauth integration. As a result a pletora of implementations appeared both Spring and community lead.
There were some nagging issues that we started running into though. Speaking from my personal point of view:
* Dealing with errors in the oauth integration and automatically initiating new oauth flows when needed wasn't available leading to all sorts of issues especially in connecting based on stored connections and requiring some ugly hacks
* No support for refresh tokens leading to complexities in the Google oauth library
* Some providers such as Facebook changed their implementations along the way which required updates to the library
Well, more than a year later, I have to say I'm disappointed in the progress. It looked like after the 1.0.x releases, the team didn't get time allocated for this library anymore and the nags weren't addressed in a timely fashion. We now missed the 1.1.0M1 release target and there seem to be a lot of issues outstanding on that one, in particular the ones that cause me the most problems in using Spring Social.
This is open source so we have to rely on the efforts of the team and the community and therefore can't "complain". I do want to voice my concern on this though. The project is not getting the love it needs.
Kind regards,
Marc