Ideas on how to not include connection string in JSON file #475
-
Hi everyone, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
That's a great question! In many corporate environments a linked table may use Active Directory integrated authentication, so no sensitive credential information is stored in the source files. But for other types of databases or authentication strategies, there IS sensitive information stored in these connection strings, and you are exactly right, that these really should not be committed to version control. The good news is that a few months ago I added support for using I would suggest that you create a new issue as a suggested enhancement for this add-in, and we can collaborate the development discussion around the issue. |
Beta Was this translation helpful? Give feedback.
That's a great question! In many corporate environments a linked table may use Active Directory integrated authentication, so no sensitive credential information is stored in the source files. But for other types of databases or authentication strategies, there IS sensitive information stored in these connection strings, and you are exactly right, that these really should not be committed to version control.
The good news is that a few months ago I added support for using
.env
files to store sensitive credentials for external database connections. (See #415) This functionality could probably be extended for use with linked tables (and pass-through queries, and other objects using a connec…