贤者一 API - unsupported_grant_type

Question

我正在尝试通过遵循 docs using Guzzle(v6) / Laravel 5.2 获取 Sage One API 的访问令牌（Laravel 的参与与这个问题），卡在了"request access token"阶段。

错误

Client error: `POST https://api.sageone.com/oauth2/token` resulted in a
 `400 Bad Request` response: {"error":"unsupported_grant_type"}

违规代码

    $client = new Client([
        'base_uri'=>'https://api.sageone.com',
        'headers' => ['content_type' => 'application/x-www-form-urlencoded']
    ]);
    $data = [
        'client_id' => getenv('SAGE_CLIENT'),
        'client_secret' => getenv('SAGE_SECRET'),
        'code' => $request->code,
        'grant_type' => 'authorization_code',
        'redirect_uri'=>'https://myurl.com/sage/refresh'
    ];

    $response = $client->request('POST','/oauth2/token',['json' => $data]);

文档状态 "grant_type - The type of grant the code relates to. Either authorization_code or refresh_token."，我都试过了。其他变量都很好而且很漂亮，只是 grant_type 似乎失败了。

更新 1 调试 header 生成以下输出。

* Hostname in DNS cache was stale, zapped * Trying 52.49.116.133... 
* Connected to api.sageone.com (52.49.116.133) port 443 (#0) 
* CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none 
* ALPN/NPN, server did not agree to a protocol 
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 
* Server certificate: 
* subject: CN=api.sageone.com,O=The Sage Group PLC,L=Newcastle Upon Tyne,ST=Newcastle Upon Tyne,C=GB,serialNumber=02231246,businessCategory=Private Organization,incorporationCountry=GB 
* start date: May 12 00:00:00 2014 GMT 
* expire date: May 11 23:59:59 2016 GMT 
* common name: api.sageone.com 
* issuer: CN=GeoTrust Extended Validation SSL CA - G2,O=GeoTrust Inc.,C=US > POST /oauth2/token HTTP/1.1 Host: api.sageone.com content_type: application/x-www-form-urlencoded User-Agent: GuzzleHttp/6.1.1 curl/7.43.0 PHP/5.6.18 Content-Type: application/x-www-form-urlencoded Content-Length: 216 
* upload completely sent off: 216 out of 216 bytes < HTTP/1.1 400 Bad Request < Content-Type: application/json < Date: Tue, 08 Mar 2016 10:53:09 GMT < Server: openresty < Content-Length: 26 < Connection: keep-alive < 
* Connection #0 to host api.sageone.com left intact

Answer 1

您正在 POST-ing 值作为 JSON 编码数据，但您应该 POST 使用表单编码。参见：http://docs.guzzlephp.org/en/latest/request-options.html#form-params，所以

$response = $client->request('POST','/oauth2/token',['form_params' => $data]);

编辑：

您应该再次检查您的代码，因为我刚刚验证并仔细检查了此更改是否使其适用于 live sage 环境。我使用的完整代码：

<?php
require 'vendor/autoload.php';

$client = new GuzzleHttp\Client([
        'base_uri'=>'https://api.sageone.com',
        'headers' => ['content_type' => 'application/x-www-form-urlencoded']
    ]);

$data = [
    'client_id' => getenv('SAGE_CLIENT'),
    'client_secret' => getenv('SAGE_SECRET'),
    'code' => getenv('SAGE_CODE'),
    'grant_type' => 'authorization_code',
    'redirect_uri'=>'https://myurl.com/sage/refresh'
];

$response = $client->request('POST','/oauth2/token',['form_params' => $data]);

echo $response->getBody();

?>

Answer 2

将 json 用于 oAuth 确实不正确：https://www.rfc-editor.org/rfc/rfc6749#section-4.1.3 我认为，这是不正确的：

$response = $client->request('POST','/oauth2/token',['json' => json_encode($data)]);

相反，我会尝试这样的事情：

$response = $client->post('/oauth2/token', [], $data);

或这个

$response = $client->post('/oauth2/token', ['body' => $data]);

另一个问题，第一个电话怎么样 https://www.sageone.com/oauth2/auth - 打通了吗？

贤者一 API - unsupported_grant_type

Sage One API - unsupported_grant_type

php

api

oauth-2.0

guzzle

sage-one