Considerations when choosing REST token storage. pros and cons of the old (file-based) and the new (DB-based) approach

Considerations when choosing REST token storage

Since version 2.1 in COZYROC SSIS+ access tokens used by REST Connection Manager can be stored not only in the file system, but also in a database (SQL Server).

 

Using such a centralized storage addresses the following complications with the file-based storage:

1.  Eliminate the need to copy the token file to the production server as an additional deployment step.
   
2. ​ Eliminate problems with services that employ non-reusable refresh tokens. Many third-party services that use OAuth 2.0 (e.g. Google services) send a refresh token that can be used only once. Thus if the same token file is copied on several machines (development, staging, production), refreshing a token on one of them will invalidate the refresh tokens on all other machines. A centralized storage eliminates this problem, as upon access token expiration, a new access and refresh token would be readily available for all servers.
   

 Specifying a path for the token file on a network share, which is accessible by the development machines and the production/staging servers, is a good alternative to using the Database storage.