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.
Note the comment the end of that issue's description, regarding the applicability of HTTP Basic in Spring Source's connection support. That is, it only makes sense if the API exposes user-oriented endpoints and if instead of an access token, the API accepts the *user's* credentials. If the API only exposes application-specific endpoints and takes some application's key/secret as credentials, then connections don't make much sense.
With that in mind, is there a specific API that you're looking to use Spring Social with that requires HTTP Basic instead of OAuth? Is it a user-centric API or an application-centric API?
Although it's not a high priority to add HTTP Basic support, one shortcut (of sorts) is to fork Spring Social, implement the necessary pieces, then submit a pull request. After some review on my part and perhaps some adjustment on your part, I can merge it into the code and suddenly Spring Social support HTTP Basic connections.
I started with a "let's give it a try" kind of mindset, I got hooked right away.
I actually emailed you a while ago (found your email here ) 'cause at first I couldn't get anything started, and I wasn't sure this was the right place to "publicly" ask for help.
But as it happens, I managed to roll it and it's going quite smoothly.
I'll be contacting you once i get it to 99% and ask for you review (if that's how it works).
As for the Basic Auth ConnectionFactory, I'll give a try at that too and let you know. What do you say?
By all means, if you want to try your hand at creating a HTTP Basic connection factory, then go ahead. Just fork Spring Social, write the necessary bits, then when you're ready submit a pull request. I'll be happy to consider it. Warning: I may nitpick on your code, so be sure to at least (1) write good tests and (2) try to follow the coding style already followed in Spring Social. (For your own extension, you are free to use whatever style you want, but code that will be merged into Spring Social needs to follow our conventions.)
Regarding Spring Social Miso: May I add that to the list and maybe even Tweet about it to let the greater Spring Social community know? Maybe you'll get some community help in testing it or fleshing out any incomplete stuff. (Open Source is awesome...Open Source on GitHub even better.)