My apologies for the extremely late support and code fix. I have been working on my employer's new project. Seeing that they want to include OAuth on their application, I thought it was a good time to update this library. Hopefully this will be my final JOAuth release (as I've decided to move forward to creating an OAuth framework).
JOAuth 1.3.1 is a release to conform to RFC 5849 strict. This allows OAuth to conform to Strict OAuth Service Providers, such as LinkedIn (which conforms to OAuth1a specification).
The code has been simplified, fixed and included support for HTTP parameters with multiple values (on a key).
I have demonstrated (below) a simple example on how OAuth 1 can be done (using Twitter, of course, as well as Facebook) to retrieve authorization tokens. The former uses OAuth 1 (lenient), while the latter uses OAuth 2 (draft 0). It's up to the developer to understand the OAuth authorization flow.
I hope that you enjoy using OAuth library as much as I had fun working on the fix. JOAuth still has the service to receive authorization tokens (just look at the joauth tag on StackOverflow on how to apply it on yours).
If you have used the previous version of JOAuth, please update your code errors, as some methods on the consumer (particularly OAuth1Consumer) has changed. Oh, did I mention that I Mavenized JOAuth? :-)
Download here.
Enjoy!
LinkedIn Example:
Facebook Example:
JOAuth 1.3.1 is a release to conform to RFC 5849 strict. This allows OAuth to conform to Strict OAuth Service Providers, such as LinkedIn (which conforms to OAuth1a specification).
The code has been simplified, fixed and included support for HTTP parameters with multiple values (on a key).
I have demonstrated (below) a simple example on how OAuth 1 can be done (using Twitter, of course, as well as Facebook) to retrieve authorization tokens. The former uses OAuth 1 (lenient), while the latter uses OAuth 2 (draft 0). It's up to the developer to understand the OAuth authorization flow.
I hope that you enjoy using OAuth library as much as I had fun working on the fix. JOAuth still has the service to receive authorization tokens (just look at the joauth tag on StackOverflow on how to apply it on yours).
If you have used the previous version of JOAuth, please update your code errors, as some methods on the consumer (particularly OAuth1Consumer) has changed. Oh, did I mention that I Mavenized JOAuth? :-)
Download here.
Enjoy!
LinkedIn Example:
Facebook Example:
> Hopefully this will be my final JOAuth release
ReplyDelete> (as I've decided to move forward to creating a
> new OAuth framework).
Just when I've decided to use JOAuth in my application... no, thank you! I need stable library code that is supported and developed.
You will realize that many OAuth Java libraries are already stable and not developed. JOAuth is constantly supported (as I use it myself). OAuth 2 will only be supported as the specification keeps changing. I have decided to create an OAuth framework as there are developers who want to add their own functionality to the OAuth protocol, i.e. implement their own nonce generator, and token strings, etc.
Delete