I thought I'd mention that LinkedIn is now supporting OAuth 1.0a requests for our Open API program (http://developer.linkedin.com/docs/DOC-1008). Since this is a new program we decided to not support legacy 1.0, which has resulted in some short-term pain.
The good news is that these changes have pushed 1.0a into more client libraries, plus we're also seeing a number of new client implementations of OAuth. Issues we've encountered are documented here: http://developer.linkedin.com/docs/DOC-1121 Specifically we found that some clients were not properly processing the oauth_token_secret, many had problems with timestamps, and there's some confusion about empty parameters being used as part of the signature base string. Again, thanks to the entire community for the libraries and support. -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
