I’m attempting to communicate with an API which requires each request to sign messages in accordance with draft-cavage-http-signatures-10 and the requirements imposed by XS2A Framework Implementation Guidelines v1.1, which requires signing using the RSA-SHA256 algorithm.
My initial idea was to simply use a pre-request script on the collection to generate this signature header, seeing as I already use it to set the RFC 2822 HTTP Date and SHA-256 message digest used in the execution of the request.
However, CryptoJS doesn’t support RSA, and it’s the only crypto library available in the Postman Sandbox. So I’m sort of stuck, unless I implement a RSA-SHA256 signing algorithm myself.
Now, I’ve noticed that crypto-js hasn’t had a single commit for a year on GitHub, which makes me ask;
- Has Postman considered other options for their sandbox to replace CryptoJS?
- Has Postman considered any other mechanism for easily adding “dynamic header values”, such as Date, Digest, and Signature?
The workaround we’re using today is to run each request through a custom reverse proxy written using Node.js and Koa, but we’d much rather do this entirely in Postman if possible, since the reverse proxy part complicates both manual and automated testing.