通过Gmail API批量获取指定ID邮件时遇401认证错误求助

我们尝试通过Gmail API的批量请求功能，传入包含邮件ID的messagesList来获取指定Gmail邮件，实现了getGmailMessagesBatch函数，但解析响应时收到401错误，提示缺少OAuth 2认证凭证，需要解决该问题以成功获取指定ID的邮件。

实现代码 #

function getGmailMessagesBatch(oauth2Client, messagesList){
var batchBody = [];
var indReq = '';
if(oauth2Client && oauth2Client.credentials && oauth2Client.credentials.access_token){
/*根据Gmail API文档生成批量请求的请求体
将多个API调用合并为一个请求，每个请求作为请求体的一部分，具体实现如下
详情请参考Gmail API文档*/
_.each(messagesList,function(eachMessage){
indReq='';
indReq = "--request_boundary\n"+
"Authorization: Bearer "+oauth2Client.credentials.access_token+"\n"+
"Content-Type: application/http\n\n"+
"GET /gmail/v1/users/"+data.userEmail+"/messages/"+eachMessage.id+"\n";
batchBody.push(indReq);
})
batchBody.push("--request_boundary--\n");
batchBody = batchBody.join('\n');
//发送批量请求
rp({
uri: 'https://www.googleapis.com/batch/gmail/v1',
method: 'POST',
headers: {
"content-type": "multipart/mixed; boundary=request_boundary"
},
body:batchBody,
resolveWithFullResponse: true
})
.then(function(response){
/*响应已序列化，批量请求中每个API调用的响应由响应Content-Type头中的边界分隔，因此需要解析响应以获取实际数据*/
var parsedResponse = parseBatchResponse(response);
return cb(null, parsedResponse);
})
.catch(function(error){
sails.log.error('Error in getting messages async in eachseries',error,data);
return cb('Unexpected error!');
})
}else{
sails.log.error('Access token missing to sync emails using gmail api',data);
return cb('Authorization failure!');
}
}

错误信息 #

解析响应时收到401错误：

{"error":{"code":401,"message":"请求缺少必需的认证凭证。需要OAuth 2访问令牌、登录Cookie或其他有效的认证凭证。","errors":[{"message":"需要登录。","domain":"global","reason":"required","location":"Authorization","locationType":"header"}],"status":"UNAUTHENTICATED","details":[{"@type":"type.googleapis.com/google.rpc.ErrorInfo","reason":"CREDENTIALS_MISSING","domain":"googleapis.com","metadata":{"service":"gmail.googleapis.com","method":"caribou.api.proto.MailboxService.GetMessage"}}]}}

问题根源 #

1. 批量请求认证方式错误：Gmail API批量请求无需在每个子请求中单独添加Authorization头，应将认证信息放在主请求的头部。
2. 未定义变量：代码中使用的data.userEmail未作为函数参数传入，可能导致请求路径错误，间接触发认证问题。
3. 格式不规范：子请求的HTTP格式不符合规范，结尾缺少必要的空行，边界分隔符的拼接也存在问题。

修复步骤 #

1. 将认证头移至主请求
   移除每个子请求中的Authorization: Bearer ...行，把认证信息添加到rp请求的headers中：

headers: {
  "content-type": "multipart/mixed; boundary=request_boundary",
  "Authorization": "Bearer " + oauth2Client.credentials.access_token
},

2. 修复未定义变量
   将data.userEmail替换为函数传入的参数，比如修改函数定义为getGmailMessagesBatch(oauth2Client, messagesList, userEmail, cb)，然后在请求路径中使用该参数：

"GET /gmail/v1/users/"+userEmail+"/messages/"+eachMessage.id+"\n\n";

注意：子请求的GET行结尾需要添加两个换行符，确保格式合规。

3. 修正批量请求体格式
   子请求的构造需严格遵循HTTP规范，边界分隔符后换行，子请求的HTTP行结尾添加空行：

indReq = "--request_boundary\n" +
"Content-Type: application/http\n\n" +
"GET /gmail/v1/users/" + userEmail + "/messages/" + eachMessage.id + "\n\n";

4. 完整修复后的代码

function getGmailMessagesBatch(oauth2Client, messagesList, userEmail, cb){
  var batchBody = [];
  var indReq = '';
  if(oauth2Client && oauth2Client.credentials && oauth2Client.credentials.access_token){
    _.each(messagesList,function(eachMessage){
      indReq = "--request_boundary\n" +
      "Content-Type: application/http\n\n" +
      "GET /gmail/v1/users/" + userEmail + "/messages/" + eachMessage.id + "\n\n";
      batchBody.push(indReq);
    })
    batchBody.push("--request_boundary--");
    batchBody = batchBody.join('');
    
    rp({
      uri: 'https://www.googleapis.com/batch/gmail/v1',
      method: 'POST',
      headers: {
        "content-type": "multipart/mixed; boundary=request_boundary",
        "Authorization": "Bearer " + oauth2Client.credentials.access_token
      },
      body: batchBody,
      resolveWithFullResponse: true
    })
    .then(function(response){
      var parsedResponse = parseBatchResponse(response);
      return cb(null, parsedResponse);
    })
    .catch(function(error){
      sails.log.error('Error in getting messages batch', error);
      return cb('Unexpected error!');
    })
  }else{
    sails.log.error('Access token missing to sync emails using gmail api');
    return cb('Authorization failure!');
  }
}

额外注意事项 #

• 确保oauth2Client的access_token未过期，若过期需先刷新令牌。
• 确认Google Cloud Console中已启用Gmail API，且OAuth 2.0客户端ID的权限范围包含https://www.googleapis.com/auth/gmail.readonly或所需的其他权限。

内容的提问来源于stack exchange，提问作者Yashwant Yadav