You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
It would be nice if, for those on a Windows machine, there were a way to connect to a database instance using Windows Authentication. While I am not sure if the "web.config" is able to handle different connection strings, but the json formatted object has user and password attributes, which are not the format required for Windows Authentication
Suggested Solution
Is it possible to use the System.Security.Principal namespace to grab and/or validate the credentials? Or is there a way to store connection strings where user and password are not required? Instead have an optional field called "Integrated Security" which can be true or false?
Other Information
It could very well be that the Web.config is better able to handle less structured connection strings, but it was not clear to me in reading the documentation. Also, personally I am used to c# web.configs (along with the structure) -- I am unclear how a Web.config file for this application should be structured. Is it xml? What is the hierarchy? This feature request could very well be covered by this. If so, please include a sample Web.config.
The text was updated successfully, but these errors were encountered:
Describe the Feature
It would be nice if, for those on a Windows machine, there were a way to connect to a database instance using Windows Authentication. While I am not sure if the "web.config" is able to handle different connection strings, but the json formatted object has user and password attributes, which are not the format required for Windows Authentication
Suggested Solution
Is it possible to use the System.Security.Principal namespace to grab and/or validate the credentials? Or is there a way to store connection strings where user and password are not required? Instead have an optional field called "Integrated Security" which can be true or false?
Other Information
It could very well be that the Web.config is better able to handle less structured connection strings, but it was not clear to me in reading the documentation. Also, personally I am used to c# web.configs (along with the structure) -- I am unclear how a Web.config file for this application should be structured. Is it xml? What is the hierarchy? This feature request could very well be covered by this. If so, please include a sample Web.config.
The text was updated successfully, but these errors were encountered: