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
Rust
No.
Like Java SDK, which provides an authorization header containing credentials and signature information.
Header authorization format: MQv2-HMAC-SHA1 Credential={}, SignedHeaders=x-mq-date-time, Signature={}
authorization
SHA1 is not recommended due to security reasons, we could consider using SHA2 instead.
No response
The text was updated successfully, but these errors were encountered:
[ISSUE #526] feat(rust): support ak/sk authorization (#527)
fa8b4cb
* feat(rust): support ak/sk authorization Signed-off-by: SSpirits <[email protected]> * feat(rust): change ak/sk type to option Signed-off-by: SSpirits <[email protected]> * Make code idiomatic Signed-off-by: Li Zhanhui <[email protected]> * feat(rust): fix license Signed-off-by: SSpirits <[email protected]> * feat(rust): optimize code Signed-off-by: SSpirits <[email protected]> * feat(rust): fix msrv test Signed-off-by: SSpirits <[email protected]> * fix(rust): fix msrv test Signed-off-by: SSpirits <[email protected]> --------- Signed-off-by: SSpirits <[email protected]> Signed-off-by: Li Zhanhui <[email protected]> Co-authored-by: Li Zhanhui <[email protected]>
Successfully merging a pull request may close this issue.
Programming Language of the Client
Rust
Is Your Feature Request Related to a Problem?
No.
Describe the Solution You'd Like
Like Java SDK, which provides an authorization header containing credentials and signature information.
Header
authorization
format:MQv2-HMAC-SHA1 Credential={}, SignedHeaders=x-mq-date-time, Signature={}
Describe Alternatives You've Considered
SHA1 is not recommended due to security reasons, we could consider using SHA2 instead.
Additional Context
No response
The text was updated successfully, but these errors were encountered: