We've investigating now. We can reproduce the problem, but don't have any ideas (yet) as to what's causing the issue. We follow LinkedIn's developments pretty closely, and they haven't announced any big changes for today (or recently).
There is a migration to go from Oauth 1a (what we support) to Oauth 2.0. That's something we will be migrating too, but it simply isn't necessary yet and LinkedIn has stressed many, many times that moving isn't necessary.. and there certainly isn't a deadline.
I'll keep you posted on what we find. Hopefully, we'll have it narrowed down soon.
Well, when I posted that comment, things weren't working. The moment we started trying to dig into things, it started working across 3 different sites (here, a localhost development and a 'live' development one).
I'm not sure what to make of it. I'll keep logging out and in periodically, but don't have any great answers other than 'flakiness'. If you see the problem again, please go into the Configuration area of JLinked and enable the "Display API Errors On Front-End:". If there are any extra messages that come up, please let us know exactly what it states. That may help us narrow down at least where the failure point is and investigate if we're doing something (partially) wrong causing the intermittent-ness.
Yup, we're in the process of diagnosing it now. There's other people posting the same issue in the LinkedIn developer area, so I don't think it's specific to JLinked. However, if there's a way around it, we'll be looking right now (while it's down).
Other bug reports:
http://developer.linkedin.com/forum/oau … nd-point-0
http://developer.linkedin.com/comment/2 … ment-24215 (latest few posts of a very long thread)
Here's the $response array that I'm getting from LinkedIn. Dunno if it helps any...
string(181) "\"white\" FGCOLOR=\"black\">
Unable to process requested URL.
string(408) "Authorization: OAuth realm="http%3A%2F%2Fapi.linkedin.com",oauth_version="1.0",oauth_nonce="6f9914b5e36a355a0a4e9c0ed3521c4e",oauth_timestamp="1366986139",oauth_consumer_key="wkhs26bgcvim",oauth_callback="http%3A%2F%2Fdev.engageapro.com%2Findex.php%3Foption%3Dcom_jlinked%26task%3DlinkedInCallback%26return%3DLw%3D%3D",oauth_signature_method="HMAC-SHA1",oauth_signature="eLeUay9Pb%2Fkk%2Bngv%2BsPPnbwpDxA%3D""
Just want to circle back on this. We haven't been able to recreate this issue today and the support requests (on LinkedIn's developer site) also seem to indicate other users are seeing things have cleared up.
Are you still having issues? Hopefully not, but if so, let us know. We're definitely sorry for the inconvenience, but it fully seemed to be an issue on LinkedIn's end.
Yup. Never fun, but part of the price of integration with any 3rd party service. LinkedIn's been very stable for the last year, but they seem to be doing a bit of work behind the scenes now. Likely, that will be a good thing in the long run, but we'll have to see what they're up to
As always, keep us posted if anything else crops up!