Signature length not correct: got 128 but was expecting 256和 got 256 but was expecting 128-自查方案

简介: 说明:    以下错误是支付宝公钥(alipay_public_key)与签名类型(sign_type)不匹配导致   Signature length not correct: got 128 but was expecting 256(签名长度不正确:得到128,但预期为256)   S...

说明:

    以下错误是支付宝公钥(alipay_public_key)与签名类型(sign_type)不匹配导致

   Signature length not correct: got 128 but was expecting 256(签名长度不正确:得到128,但预期为256)

   Signature length not correct: got 256 but was expecting 128 (签名长度不正确:得到256,但预期为128)

    Signature length not correct: got 257 but was expecting 256(签名长度不正确:得到257,但预期为256)

解决方案:

    首先:检查请求参数查看自己的sign_type=RSA还是RSA2

    如果是RSA:请使用1024位支付宝公钥(如下图)

    如果是RSA2:请使用2048位支付宝公钥(如下图)

    RSA2类型特别说明:如果您的appid是2018年1月五号之后创建的只能使用RSA2签名类型详情查看公告

    支付宝公钥查看地址(填写自己的请求appid放到浏览器中进行访问登录查看自己的支付公钥):[url]https://openhome.alipay.com/platform/detailApp.htm?appId=[/url]此处填写您的请求appid&tab=appDetail

    如果您检查了自己的签名类型和支付宝公钥是对应关系,还是一样报错 欢迎在帖子下方追问12

目录
相关文章
sign check fail:check Sign and Data Fail报错攻略
错误码: com.alipay.api.AlipayApiException: sign check fail: check Sign and ​Fail            报错原因:验签失败 ,未使用正确的支付宝公钥     在新版接口的调用过程中,常常出现此报错。
4936 12
|
程序员
check sign Fail!或sign check fail: check Sign and Data Fail!-自查方案
一、报这个错大多都是支付宝公钥配置错误,不同环境的公钥是不同的,大家先确认自己的支付宝公钥获取是否正确:  1. 沙箱公钥【查看】 密钥生成可参照【如何生成RSA,RSA2密钥】  2. 开放平台密钥【查看】,已创建应用的,直接打开对应的应用进行查看, 创建应用可参照:【如何创建应用】 打开应用查...
1997 12
|
9月前
|
缓存 数据安全/隐私保护 Windows
ECDSA host key for ... has changed and you have requested strict checking.Host key verification fail
ECDSA host key for ... has changed and you have requested strict checking.Host key verification fail
Input operand 1 has a mismatch in its core dimension 0, with gufunc signature (n?,k),(k,m?)->(n?,m?)
Input operand 1 has a mismatch in its core dimension 0, with gufunc signature (n?,k),(k,m?)->(n?,m?)
420 0
Input operand 1 has a mismatch in its core dimension 0, with gufunc signature (n?,k),(k,m?)->(n?,m?)
|
JSON 数据格式
遇到【Unexpected character (‘“‘ (code 34)): was expecting comma to separate Object entries】的解决办法
遇到【Unexpected character (‘“‘ (code 34)): was expecting comma to separate Object entries】的解决办法
遇到【Unexpected character (‘“‘ (code 34)): was expecting comma to separate Object entries】的解决办法
工银e生活开发脱坑日志(7)Missing argument 6 for IcbcSignature::verify()
工银e生活开发脱坑日志(7)Missing argument 6 for IcbcSignature::verify()
89 0
使用 spritesmith 报错 Error: Invalid file signature
使用 spritesmith 报错 Error: Invalid file signature
142 0
使用 spritesmith 报错 Error: Invalid file signature
|
Java Maven Android开发
Maven项目报错invalid LOC header (bad signature)
Maven项目报错invalid LOC header (bad signature)
170 0
Maven项目报错invalid LOC header (bad signature)
config.guess: unable to guess system type、config.sub: missing argument
config.guess: unable to guess system type、config.sub: missing argument
152 0
|
Java Maven
invalid LOC header (bad signature) 错误解决办法
invalid LOC header (bad signature) 错误解决办法
676 0