Sombra Key Rotations

NIST recommends rotating keys once a year.

Transcend allows you to rotate all the keys used by Sombra, granting you greater control over your security practices when using Transcend.

Sombra remembers the four (4) latest sets of keys. Older keys are "forgotten".

If Transcend hosts your Sombra instance, you can rotate the keys by following these steps:

  1. Navigate to "Settings > Sombra" on your Admin Dashboard

  2. Scroll to the "Hosted Sombra Keys" section

  3. Click on the "Rotate Sombra Keys" button

  4. Once the keys are finished rotating, you will be presented with your new INTERNAL_KEY. You will need to copy it down, as it will be lost once the modal is closed.

  5. After the modal closes, you will be redirected to the login page for the new keys to take effect.

In the key rotation process, we rotate two keys, the INTERNAL_KEY, and the JWT_ECDSA_KEY.

If you'd like for your internal application to authenticate with Sombra's internal API, you can do so by generating a symmetric key, called the INTERNAL_KEY. This key is then supposed to be sent as a Bearer token, with the x-sombra-authentication header.

INTERNAL_KEY_BIN=$(openssl rand 32)
INTERNAL_KEY=$(echo -n "$INTERNAL_KEY_BIN" | base64)
INTERNAL_KEY_HASH=$(echo -n "$INTERNAL_KEY_BIN" | openssl dgst -binary -sha256 | openssl base64)
echo "set in your service environments: INTERNAL_KEY: $INTERNAL_KEY"
echo "set gateway environment: INTERNAL_KEY_HASH: $INTERNAL_KEY_HASH"

You can then provide the hash of the internal key into the Sombra environment like:


You can provide a CSV of internal key hashes to gracefully migrate from an old value to a new value like:




Note that it is safe to replace the INTERNAL_KEY_HASH in the environment without needing to cycle and data in your Transcend dashboard.

This is an asymmetric JSON web token key for signing Sombra payloads using the Elliptic Curve Digital Signature Algorithm. This key can also be used to derive other encryption keys used in Sombra.

The key is critical for decrypting data that is stored in the Transcend cloud and other data in the Transcend database must be migrated before you can remove an old key.

To generate a new key, you can run the command:

JWT_ECDSA_KEY=$(openssl ecparam -genkey -name secp384r1 -noout | base64)
echo "set gateway environment: JWT_ECDSA_KEY: ${JWT_ECDSA_KEY}"

You should then set the new key in the environment along side the old key:




It is recommended that you leave the old key around to decrypt data that was encrypted using that key. The first key in the CSV will be used to encrypt all data going forward. If you need to do an urgent key rotation, please reach out to to assist to make sure no data is corrupted or lost during the cycle.

  1. Navigate to "Settings > Sombra" on your Admin Dashboard

  2. Scroll down to the "Request Security" section of the page

  3. Click on the "Re-Sign Encryption Contexts" button to update any requests that are failing due to the error Request's encryption context has expired...

  1. Navigate to "Settings > Sombra" on your Admin Dashboard
  2. Scroll down to the "Request Security" section of the page
  3. Click on the "Re-Sign SaaS Contexts" button to update all integrations in your organization