mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #2015] [feature]: how to use sha256 in Pre-request Scripts Scripts #657
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#657
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zlay0701 on GitHub (Dec 16, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2015
Originally assigned to: @jamesgeorge007 on GitHub.
Is there an existing issue for this?
Summary
how to use sha256 in Pre-request Scripts Scripts?
Why should this be worked on?
Some interfaces need to dynamically generate signatures and initiate requests according to tokens
The signature algorithm uses algorithms such as sha256 and SHA1
@liyasthomas commented on GitHub (Dec 16, 2021):
Similar issue: #2001
Adding support to
npm packagesand SDKs are in our roadmap. Stay tuned for product updates.@apptut commented on GitHub (Dec 19, 2021):
npm packages +1, I want gen sign with params by md5 or sha1
@AndrewBastin commented on GitHub (Dec 19, 2021):
Hate to burst the bubble, but I am not planning on getting NPM packages as is to work with Hoppscotch scripting environment.
It's a complicated enough task as is and implementing mechanisms to manage NPM and node_modules and dependency management and Node Module Resolution capabilities (remember, the scripts are executed client side in a sandbox) all within the sandbox is a massive challenge which we cannot spend too much effort on.
But, I was hoping to get Deno style ESM URL imports working so you can directly import from URL (read more here: https://deno.land/manual/examples/import_export) and there are sources like JSPM, Skypack and Unpkg (as an option) which give all the important libraries in the ESM format.
@apptut commented on GitHub (Dec 20, 2021):
I agree with what you said. My purpose is not to import npm, but to get the capabilities of encryption libraries. Many times the interface needs to be signed using md5, or sha1, base64 algorithms, and so on.
@zlay0701 commented on GitHub (Jan 11, 2022):
can add https://github.com/brix/crypto-js ?
@evanlurvey commented on GitHub (Mar 6, 2023):
I also have needed crypto-js before for auth and signatures.
@sneha-herle commented on GitHub (Aug 10, 2023):
Please find a solution for this, needed crypto-js before for auth and signatures.
@bappleug-tw commented on GitHub (Aug 26, 2023):
Plus one for adding crypto-js support
@jhoos70 commented on GitHub (Oct 18, 2023):
Need crypto-js, too. Without it hoppscotch is useless for my usecase.
@samuel-deal-tisseo commented on GitHub (Oct 19, 2023):
Plus one for adding crypto-js support
@qichengri commented on GitHub (Jan 5, 2024):
Plus one for adding crypto-js support
@archcorsair commented on GitHub (Apr 15, 2024):
Any updates on this? This feature is the only one preventing us from moving from postman to hoppscotch
@siniradam commented on GitHub (May 7, 2024):
Seems like some crypto features available in the browser API working, if you someone is in dire need of HMAC, maybe can give it a try to this function.
@alizufan commented on GitHub (Jun 27, 2024):
thank you !
@jamesgeorge007 commented on GitHub (Nov 6, 2025):
Hi! #5090 added the ability to import ESM packages in the scripting context as part of the
Experimental scripting sandbox. You can now import crypto libraries directly:We're aware of certain limitations with the native
cryptomodule. ESM imports offer an alternative approach. Ongoing scripting improvements are tracked in #5221.In the meantime, you can choose to proceed with either of the following:
Experimental scripting sandbox.cryptomodule.@jamesgeorge007 commented on GitHub (Jan 28, 2026):
Closing as this is addressed in v2026.1.0 via #5791.