We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
按照我的理解:
/sn
我复制了你的代码来运行,一直卡在sn验证那里。
然后仔细看了看/sn接口和签名发现了问题:
MD5(MD5(参数字符串)+MD5(config配置信息))
SignDemo
MD5(config配置信息)
小白第一次接触后台开发,不知道我这样理解和修改是否正确?谢谢了
The text was updated successfully, but these errors were encountered:
我觉得也是有点问题的,首先请求/sn接口拿到签名,之后走/v2时候携带签名,但是原create签名考param拼接的str生成,也就createSign根据每次的req携带的param不同,产生不同的签名。这或许是单体小demo没有更细思考导致的
Sorry, something went wrong.
/sn是默认参数,/v2接口是依赖动态请求参数哇。生成签名要一致性,只依赖config就行了
No branches or pull requests
按照我的理解:
/sn
接口,获取sn和ts信息我复制了你的代码来运行,一直卡在sn验证那里。
然后仔细看了看
/sn
接口和签名发现了问题:MD5(MD5(参数字符串)+MD5(config配置信息))
组成,但调用/sn
接口生成sn时,在SignDemo
方法中,签名的参数字符串是空或者默认值,这样就会导致,请求中参数中的sn和比对时的sn不一致MD5(MD5(参数字符串)+MD5(config配置信息))
改成MD5(config配置信息)
的形式,就能验证通过了小白第一次接触后台开发,不知道我这样理解和修改是否正确?谢谢了
The text was updated successfully, but these errors were encountered: