Mike,
If you are new to OAuth, I suggest you play with the OAuth Java
Library in a servlet without JAX-RS first so you can use the examples
provided. You may come to the conclusion that JAX-RS isn't the right
technology for this, like we did. JAX-RS may buy you something if you
plan to use WADL.
iPhone apps can register custom protocol handlers and then pass a callback
url like "apphandler://callback/url/here"
There is a detailed explanation of how this process works that I found
here:
http://www.mobileorchard.com/apple-approved-iphone-inter-process-communication/
I'm pretty sure that thi
On Sun, Jul 26, 2009 at 8:12 AM, Ethan Jewett wrote:
>
> iPhone apps can register custom protocol handlers and then pass a callback
> url like "apphandler://callback/url/here"
> There is a detailed explanation of how this process works that I found here:
> http://www.mobileorchard.com/apple-appr
On Fri, Jul 24, 2009 at 6:49 PM, John Kristian wrote:
>
> The third parameter to getRequestToken is sent to the server, not
> passed to the HTTP client library. This should work better:
>
> OAuthClient client = ...
> client.getHttpParameters().put(HttpClient.CONNECT_TIMEOUT, 3*1000);
> client.get
John/Zhihong,
I would like to add something to the 'client being uprotected with the
consumer secret'.
A client can be a reliable consumer if it protects the secret. It's
true that clients are easier to crack then a consumer that is a web
server, but again the server consumer can also be broken.
I've read that an iPhone app can't retrieve Key Chain items that were
stored by other apps.
http://www.softwareops.com/blogs/iPhone/iPhoneDevBlog_files/b4452aa19b4b4d6fb2a7c149dbacaa75-33.html
If true, the Key Chain would be a good place to store token secrets.
On Jul 26, 11:25 am, Monis wrote:
