Data stored in the application's web.config file is highly sensitive. Therefore, you may want to keep it secure by encrypting its contents. Encryption provides greater security because it converts the contents into an unreadable format.
Overview
You must have Diocesan Admin permissions to view this page.
The features on the Encryption and Decryption page enable you to encrypt (or decrypt) the contents of two sections of the web.config file:
- appSettings
- connectionStrings
Encryption of these sections is recommended because they contain highly sensitive data.
web.config File Sections
You can use encryption to protect sensitive data in these sections of the web.config file:
- appSettings: used to store connection strings, server names, file paths, and other settings that enable the application to perform.
- connectionStrings: used to store information needed by the provider to initiate a connection to your database or data files. The connection string may include the server and database names, as well as security information such as the username and password. If anyone needs to access the database information for your application, the first place they will look is the web.config file.
Buttons
: automatically encrypts the information in the section. Encryption provides more security because the contents are changed into an unreadable format.
: decrypts the information in the section. Decryption offers no security because the contents remain in their original format, making them easily readable. If you need to see the specific value for a setting, you can decrypt the section.
Updated