Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
insomnia-plugin-ovhcloud-signature
Advanced tools
This is a plugin for [Insomnia](https://insomnia.rest/) that generates the `X-Ovh-Signature` signature header for API calls to the [OVH Cloud API](https://docs.ovh.com/gb/en/api/first-steps-with-ovh-api/#first-api-usage).
This is a plugin for Insomnia that generates the X-Ovh-Signature
signature header for API calls to the OVH Cloud API.
OVH Cloud API calls require that once you have obtained your three keys (AK, AS, CK), you need to sign all API requests. The signature is calculated as follows:
SHA1_HEX(AS+"+"+CK+"+"+METHOD+"+"+QUERY+"+"+BODY+"+"+TSTAMP)
Install the insomnia-plugin-ovhcloud-signature
plugin from Preferences -> Plugins.
Generate your Application Keys. Once you have created the keys, you will be issued three keys:
You will need to add your own headers for:
X-Ovh-Application
with the value of the Application KeyX-Ovh-Consumer
with the value of the Secret Consumer KeyYou can template these in a private environment like:
{
"ApplicationKey": "1234567890abcdef",
"ApplicationSecret": "1029384756abcdef",
"ConsumerKey": "0987654321defabc"
}
Then using a plugin like the Global Headers you can set your Base Environment to be something like:
{
"basePath": "https://api.ovh.com/1.0",
"GLOBAL_HEADERS": {
"Accept": "application/json",
"Content-Type": "application/json;charset=utf-8",
"X-Ovh-Application": "{{ApplicationKey}}",
"X-Ovh-Consumer": "{{ConsumerKey}}"
}
}
Add the OVH Signature
template tag to a request header.
Provide the values manually or from your private environment variables:
NB: Ignore the Live Preview error
The plugin will generate and add the headers:
X-Ovh-Timestamp
X-Ovh-Signature
Because of the way PUT
and POST
methods need the JSON body included in the signature, currently the body of your request needs to be minified with no spaces, for example when editing a credential with PUT
on the /1.0/me/api/credential/<credentialId>
endpoint:
The body might be like this, and must be fully minified.
{"allowedIPs":["127.0.0.1/32","127.0.0.2/32"]}
This results in the insomnia request Timeline being:
> PUT /1.0/me/api/credential/553184188 HTTP/1.1
> Host: api.ovh.com
> User-Agent: insomnia/2022.6.0
> Content-Type: application/json
> Accept: application/json
> X-Ovh-Application: 1234567890abcdef
> X-Ovh-Consumer: 0987654321defabc
> X-Ovh-Timestamp: 1667135223
> X-Ovh-Signature: $1$0987654321123456789009876543211234567890
> Content-Length: 51
| {"allowedIPs":["127.0.0.1/32","127.0.0.2/32"]}
If there are spaces in your JSON body, the plugin currently can't generate a matching signature. A future TODO for sure.
FAQs
This is a plugin for [Insomnia](https://insomnia.rest/) that generates the `X-Ovh-Signature` signature header for API calls to the [OVH Cloud API](https://docs.ovh.com/gb/en/api/first-steps-with-ovh-api/#first-api-usage).
We found that insomnia-plugin-ovhcloud-signature demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.