在LinkedIn上找不到方法的POST https://www.linkedin.com/uas/oauth2/accessToken HTTP/1.1结果 [英] POST https://www.linkedin.com/uas/oauth2/accessToken HTTP/1.1 results in Method Not Found on LinkedIn
问题描述
我正在使用LinkedIn Owin Middleare，今天早晨开始遇到问题，现在将其重现为以下错误:
I am using the LinkedIn Owin Middleare and started running into issues this morning and have now reproduced it to the below error:
POST https://www.linkedin.com/uas/oauth2/accessToken HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Host: www.linkedin.com
Cookie: bscookie="v=1&201504071234373bc02b47-9d08-477f-8375-b80b281ef416AQEptFjv8jXPI93YmF-H-3kvnwSLwBF8"; bcookie="v=2&46f6f299-6702-48bf-8634-7ba023bd5099"; lidc="b=LB23:g=218:u=215:i=1428412320:t=1428487523:s=AQEQQq6vlEKPT3LW8c0cPEzRTKp-ToxL"
Content-Length: 267
Expect: 100-continue
Connection: Keep-Alive
grant_type=authorization_code&code=AQQRSgEH8vczSFJKNxtMpunzjYN6YJxoF2hiX_d9RVkqBvMC7TzRpur0p9NJFdQOUNf8RmFyj_cCg3ENTucRw5e-gQfEZ5sPGoujiFRsQ8Tb0pLnaog&redirect_uri=http%3A%2F%2Flocalhost%3A1729%2Fsignin-linkedin&client_id=&client_secret=
找不到方法的结果.
HTTP/1.1 405 Method Not Allowed
Date: Tue, 07 Apr 2015 13:13:16 GMT
Content-Type: text/html
Content-Language: en
Content-Length: 5487
X-Li-Fabric: PROD-ELA4
Strict-Transport-Security: max-age=0
Set-Cookie: lidc="b=LB23:g=218:u=215:i=1428412396:t=1428487523:s=AQExeP2uX-7KXQv79NIZmW0LB09uE4eJ"; Expires=Wed, 08 Apr 2015 10:05:23 GMT; domain=.linkedin.com; Path=/
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Cache-Control: no-cache, no-store
Connection: keep-alive
X-Li-Pop: PROD-IDB2
X-LI-UUID: 0FM/jIG90hPAzyhAqCsAAA==
正在寻找任何人确认linkedin上的更改导致此错误，并且不是特定于应用程序的.
Looking for anyone to confirm that there was a change on linkedin causing this error and that its not application specific.
请注意，我删除了clientid/secret之上的内容.
Note that i removed teh above clientid/secrets.
推荐答案
对于使用Owin Middleware和Owin.Security.Providers的用户
For those using Owin Middleware and Owin.Security.Providers
使用修复程序创建了预发行版nuget. https://www.nuget.org/packages/Owin.Security .Providers/1.17.0-pre
A pre-release nuget was created with a fix. https://www.nuget.org/packages/Owin.Security.Providers/1.17.0-pre
目前有效.但是，直到我们知道linkedin发生了什么变化或带有有关他们所做的更改的声明时，人们才可以使用此修补程序.
This works for now. But until we know what linkedin has changed or comes with statement about what they changed people can use this as a hotfix.
有关此修复程序的更多背景信息，请访问: https://github.com/RockstarLabs/OwinOAuthProviders/issues/87#issuecomment-90838017
Alittle more background on the fix can be found at : https://github.com/RockstarLabs/OwinOAuthProviders/issues/87#issuecomment-90838017
但是，根本原因是LinkedIn更改了accessToken端点上的某些内容，导致大多数使用linkedin SSO的库都必须应用修补程序，但我们尚未从linkedin上听到任何消息.
But the root cause is that LinkedIn changed something on there accessToken endpoint causing most of the libs using linkedin SSO had to apply a hotfix, but we yet haven't heard anything from linkedin.
这篇关于在LinkedIn上找不到方法的POST https://www.linkedin.com/uas/oauth2/accessToken HTTP/1.1结果的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
