调用:https://oapi.dingtalk.com/call_back/update_call_back接口
public OapiCallBackUpdateCallBackResponse updateCallBack(List<String> tagList) throws ApiException {
DingTalkClient client = new DefaultDingTalkClient(DingConstants.UPDATE_CALL_BACK);
OapiCallBackUpdateCallBackRequest req = new OapiCallBackUpdateCallBackRequest();
req.setCallBackTag(tagList);
req.setAesKey(DingConstants.AES_KEY);
req.setToken(DingConstants.TOKEN);
req.setUrl("http://3nezcn.natappfree.cc/callback");
OapiCallBackUpdateCallBackResponse rsp = client.execute(req, getAccessToken());
return rsp;
}
callback地址也能正常接受返回的
@RequestMapping(method = RequestMethod.POST)
@ResponseBody
public Map<String, String> post(@RequestParam(name = "signature", required = false) String signature,
@RequestParam(name = "timestamp", required = false) String timestamp,
@RequestParam(name = "nonce", required = false) String nonce,
@RequestBody(required = false) JSONObject json) {
log.debug("\n接收到来自钉钉服务器的认证消息:[{}, {}, {}, {}]", signature,
timestamp, nonce);
.........
.........
// 返回success的加密信息表示回调处理成功
return dingTalkEncryptor.getEncryptedMap(CALLBACK_RESPONSE_SUCCESS, System.currentTimeMillis(), Utils.getRandomStr(8));
return会报一下错误信息
n^_^{"errcode":71007,"errmsg":"回调地址已不存在"}
什么原因?
观察下返回的内容是什么。有没有超时
版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。