Unify and manage your data

Update an expiring or expired staging SAS token

Learn how to update an expiring or expired Azure staging SAS token for a Reltio Data Pipeline.

Reltio Data Pipelines use SAS tokens to authenticate and access Azure staging storage during data delivery. This authentication method applies to the Reltio Data Pipelines for Snowflake (Staging Pipeline) and Databricks when configured with Azure staging storage. Each SAS token has an expiration date defined when it is created. Update the token before it expires to avoid disruption to functioning of Data . If the token has expired, create and store a replacement before validating the connection.

Review SAS token expiry alerts for Reltio Data Pipelines for information about SAS token expiry alerts.

To update a Databricks staging SAS token
  1. Create a new token by following Create Staging SAS tokens for Data Pipeline Hub.
  2. Store the updated token by following Store secrets in Data Pipeline Hub (Azure).
  3. Validate the updated configuration by following Validate the Reltio-to-Azure cloud storage connection.
  4. (Optional) Synchronize missed tenant data to the destination.

    If the staging SAS token expired before you updated the token, the Data Pipeline may have missed tenant data while access to the staging storage was unavailable.

    Run the Sync to Data Pipeline API and set updatedSince to the timestamp when the Data Pipeline stopped exporting data. The API synchronizes objects updated after that timestamp. If you omit updatedSince, its default value is 0, and the API synchronizes all tenant data.

To update a Snowflake staging SAS token
  1. Generate a replacement token by following Create Azure SAS tokens for Snowflake staging.
  2. Store the updated token by following Store secrets in Data Pipeline Hub (Azure).
  3. Validate the updated configuration by following Validate the Reltio-to-Azure cloud storage connection.
  4. (Optional) Synchronize missed tenant data to the destination.

    If the staging SAS token expired before you updated the token, the Data Pipeline may have missed tenant data while access to the staging storage was unavailable.

    Run the Sync to Data Pipeline API and set updatedSince to the timestamp when the Data Pipeline stopped exporting data. The API synchronizes objects updated after that timestamp. If you omit updatedSince, its default value is 0, and the API synchronizes all tenant data.

Result

The updated staging SAS token is stored for the affected Data Pipeline, and any missed tenant data is synchronized to the destination.