Replies: 1 comment
-
|
Hi, Thank you for the detailed information. To help us investigate this issue further, could you share the following -
Additionally, could you verify that all the paths referenced in the environment configuration are valid windows paths and point to the expected files? Thank you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Insomnia Team,
On my API on Insomnia I have a series of JWE encrypted endpoints (full body and partial body encryption). I was able to successfully decrypt the responses of these endpoints using my Mac machine with configurations like the following (one example of an endpoint) in environment settings and certificates:
{
"scheme": "https",
"base_path": "",
"host": "{host name}",
"mastercard": {
"consumerKey": "{value here}",
"keyAlias": "{value here}",
"keystoreP12Path": "path to file",
"keystorePassword": "{value here}",
"appliesTo": [
"randomwebsite.com"
],
"encryptionConfig": {
"paths": [
{
"path": "/endpoint",
"toEncrypt": [
{
"element": "$",
"obj": "$"
}
],
"toDecrypt": [
{
"element": "$",
"obj": "$"
}
]
},
],
"mode": "JWE",
"encryptionCertificate": "path to file",
"keyStore": "path to file",
"keyStoreAlias": "{value here}",
"keyStorePassword": "{value here}",
"encryptedValueFieldName": "{value here}"
}
}
}
However, when I use Insomnia on my Windows machine (Exact same version, node etc.), I wasn't able to decrypt the response. On Windows for me it returns a success response but does not decrypt the response, it leaves it encrypted.
Do you have any idea what could be potentially causing this issue? Is decryption supported on Windows machines?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions