Example Signature Verification
This is an example of verifying signatures using your Keygen account's public key. You can find your public key within your account's settings page. Verifying response signatures will help prevent simple MITM attacks, where the attacker redirects traffic from your licensing server (e.g. Keygen) to their own locally controlled server, or where you have cached a validation response locally and want to verify its integrity (i.e. it has not been tampered with).
Running the example
First up, configure a few environment variables:
# Keygen product token (don't share this!) export KEYGEN_PRODUCT_TOKEN="YOUR_KEYGEN_PRODUCT_TOKEN" # Your Keygen account ID export KEYGEN_ACCOUNT_ID="YOUR_KEYGEN_ACCOUNT_ID" # Your Keygen account's public key export KEYGEN_PUBLIC_KEY=$(printf %b \ '-----BEGIN PUBLIC KEY-----\n' \ 'zdL8BgMFM7p7+FGEGuH1I0KBaMcB/RZZSUu4yTBMu0pJw2EWzr3CrOOiXQI3+6bA\n' \ # … 'efK41Ml6OwZB3tchqGmpuAsCEwEAaQ==\n' \ '-----END PUBLIC KEY-----')
You can either run each line above within your terminal session before
starting the app, or you can add the above contents to your
file and then run
source ~/.bashrc after saving the file.
Next, install dependencies with
Then run the script with the route you want to fetch:
yarn start '/licenses/442160c6-20d2-44a7-883d-245e38f651fd' yarn start '/users/dbe63060-eee7-4c87-98fa-f133fb8131fa' yarn start '/machines?page[number]=1&page[size]=5'
The above commands will only succeed if the signature verification is successful, so be sure to copy your public key correctly. You can find your public key within your account's settings page.
Reach out at firstname.lastname@example.org if you have any questions or concerns!