Azure Keyvault Sign API-请求正文的“值"编码格式 [英] Azure Keyvault Sign API - Request body "value" encoding format

查看:99
本文介绍了Azure Keyvault Sign API-请求正文的“值"编码格式的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

https:/上参考Azure keyvault Sign API/docs.microsoft.com/en-us/rest/api/keyvault/sign/sign .还不清楚值"是字符串(请求和响应中都是字符串),API如何期望像摘要这样的二进制字符串的编码以及响应如何对此值"进行编码?这是在base64中吗?如果是这样,Azure在base64上有什么区别?有任何示例代码显示此REST API请求/响应处理吗?

Referring to the Azure keyvault Sign API at https://docs.microsoft.com/en-us/rest/api/keyvault/sign/sign. Its not clear if the "value" which is string (in request and response both), how the API expects the encoding for binary strings like digest and how the response has this 'value' encoded? Is this in base64? If so, Azure has any difference in base64? Any sample code showing this REST API request/response processing?

推荐答案

对于Sign API,该值是摘要. 此页面表示它需要进行base64url编码,并符合JOSE规范.实际值将根据签名算法而有所不同.可以找到

For the Sign API, the value is a digest. This page tells that it needs to be base64url encoded, and conforming to JOSE specifications. The actual value will vary according to the signing algorithm. Links to libraries and sample code in many programming languages can be found here.

这篇关于Azure Keyvault Sign API-请求正文的“值"编码格式的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆