Deployment of SSIS packages that connect to Microsoft services

API Connectors
, , , , , ,
1

Introduction

For security reasons Microsoft Graph API uses a pattern of changing Refresh Tokens. It means that with each HTTP request a new Refresh Token is issued, which should be used in the subsequent calls (otherwise, if you use an old one, it will expire in 90 days). Therefore all ZappySys API Connectors that connect to Microsoft services such as SharePoint Online or OneDrive save Refresh Tokens to a file, once you generate the tokens:

image
image817×711 42.9 KB

However, if you don’t perform one additional step for a non-local environment (development environment) in the deployment process, you may get into trouble later on – the Refresh Token will simply stop working after several months. The tip below will save you one or two headaches.

Tip

When deploying SSIS packages that use API Connectors based on Microsoft services to other environments (e.g., production), make sure you:

  • Deploy refresh_token.json to the production server
  • Parameterize the RefreshTokenFilePath property of API Connection Manager to match the actual location of refresh_token.json

Here is where you can find where you saved the Refresh Token:

image
image761×646 39.2 KB

And here is the RefreshTokenFilePath property you are looking to parameterize:

image
image496×489 12.1 KB

Contact us

If you encounter any challenges or have specific use cases, please contact our support team via chat or ticket.