Oct 9, 2020, 4:16 PM UTC

Local time: Oct 9, 2020, 4:16 PM UTC

New Integrations

• Adds supports for Sendoso.

  

Bug Fixes

• patches a bug in the Iterable integration where the User Export would return 500 because of a timeout from large amounts of data.

• Error handling on submit new DSR now sends the employee through a redirect flow to confirm their identity.

  

• Fixes a bug that occurred with using a self-hosted Sombra gateway with multiple Transcend organizations and SAML login. The bug caused a re-login loop and prevented integrations from being connected.

Documentation Updates

• Update the documentation and public examples to respond to server integration webhooks using body.profile.identifier instead of body.coreIdentifier.value to support workflows where the server integrations do not look up by core identifier. Updated Receiving DSR docs Updated Upload to our API docs Updated GitHub examples When creating a new server integration, only access and erasure requests are defaulted on by default.

Enrichment with async responses through Sombra

We have now standardized our enricher webhooks to match the server integration webhook format.

Previously we would:

1. Transcend sends an HTTP webhook to server
2. server looks of enriched identifiers
3. server signs a JWT for each identifier
4. server responds back to webhook 200 with signedRequestIdentifiers in the webhook body

The new flow is:

1. Transcend sends an HTTP webhook to server
2. server queues job and responds back 200
3. server later queries identifiers
4. server posts identifiers to Sombra gateway as enrichedIdentifiers (no signing required)

This change is shown in this pull request on our examples repository.

See the updated docs

Note: If you are migrating an existing enricher to this new style. Please reach out to someone on the Transcend team and they will remove the public key that was previously associated with your enricher. You can remove the public/private keypair from your server environment and the signing of these identifiers will now be done by your Sombra gateway. Sombra has a built in key rotation strategy and in the future, we will recommend when your keys should be cycled on the Admin Dashboard.

This is not an issue if you create a new enricher.