Linkedin errors again

Alex,

Have you had any other reports of O-Auth errors? I only get them with the JLinked extension (my site and yours). Have they made some updates that you are not aware of perhaps?

Just curions.

- JW

It looks like it's down again.

I'd be interested to know the reason. I'll do some more debugging of the Oauth response a little later today and post back on the forum.

- JW

Here's the $response array that I'm getting from LinkedIn. Dunno if it helps any...

array(3) {
["linkedin"]=>
array(1) {
["

string(181) "\"white\" FGCOLOR=\"black\">

Unable to process requested URL.




"
}
["info"]=>
array(21) {
["url"]=>
string(82) "api.linkedin.com/uas/oauth/requestToken?...ddress+r_fullprofile"
["content_type"]=>
string(9) "text/html"
["http_code"]=>
int(400)
["header_size"]=>
int(204)
["request_size"]=>
int(564)
["filetime"]=>
int(-1)
["ssl_verify_result"]=>
int(0)
["redirect_count"]=>
int(0)
["total_time"]=>
float(0.465314)
["namelookup_time"]=>
float(0.000439)
["connect_time"]=>
float(0.079422)
["pretransfer_time"]=>
float(0.381319)
["size_upload"]=>
float(0)
["size_download"]=>
float(242)
["speed_download"]=>
float(520)
["speed_upload"]=>
float(0)
["download_content_length"]=>
float(242)
["upload_content_length"]=>
float(0)
["starttransfer_time"]=>
float(0.465281)
["redirect_time"]=>
float(0)
["certinfo"]=>
array(0) {
}
}
["oauth"]=>
array(2) {
["header"]=>
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""
["string"]=>
string(436) "POST&https%3A%2F%2Fapi.linkedin.com%2Fuas%2Foauth%2FrequestToken&oauth_callback%3Dhttp%253A%252F%252Fdev.engageapro.com%252Findex.php%253Foption%253Dcom_jlinked%2526task%253DlinkedInCallback%2526return%253DLw%253D%253D%26oauth_consumer_key%3Dwkhs26bgcvim%26oauth_nonce%3D6f9914b5e36a355a0a4e9c0ed3521c4e%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1366986139%26oauth_version%3D1.0%26scope%3Dr_emailaddress%2520r_fullprofile"
}
}

Yep. It's been a recurring issue with LinkedIn's API.

Not much we can do about that.