Best practice regarding securement of the Web.conf file

[1527460Kevin]

Hello,

 

I'm wondering what the best practice is that other passwordstate users use to secure their web.conf file. As the web.ini file contains sensitive information such as database connection strings and such its kind of a hazard to leave them like that.

 

I'm just curious how other users secure it, I was thinking of maybe using Azure Key vault for this.

Also while I'm at it. Could via the use of API's and file attachments (files with the database connection strings and such) Passwordstate be used to secure these credentials for other applications, I.E. Application to Application Password Management.

[Fabian Näf]

Hi Kevin

 

Passwordstate has a chapter in their installation instructions, about how to encrypt the sensitive data in the web.config.

You find these information in this file on page 19 and 20.

 

I would say, you can also use the function to add documents to a folder or passwordlist to securely store files from other applications (also by using the API).

 

Best regards,

 

Fabian

[1527460Kevin]

Thank you very much Fabian!