Configuration and use of ShareWAF

In previous versions, ShareWAF configuration information was read locally, such as protected websites, personalized configurations, and so on, and was stored locally. If it is used as software WAF, or small private cloud WAF. There is no problem.

However, it is inconvenient to build large-scale cloud WAF and cluster deployment, because to deploy ShareWAF on multiple machines, the configuration information is not synchronized and needs to be configured separately for different machines.

Starting from v2.0.3, when the mongodb database function is enabled, the configuration information will also be stored in a separate remote mongodb database.

The integration of configuration information will eliminate the inconvenience of previous use.

Multiple ShareWAF will share the same configuration file and the same report database (report database sharing has been available in previous versions).

Use and effect

1. To use it for the first time, you need to set use_mongodb to 1 in config.js (default is 0), and set the mongodb server address (with password).

2. When you start ShareWAF, it will display as follows:

Prompt data is submitted to mongodb (debug is displayed when it is on, and debugging information is not displayed when it is not enabled).

This is because when running for the first time, there is no data in the remote mongodb database, and ShareWAF uploads the local configuration information to the database. After that, there is configuration information in the database, and the configuration information in the database will be used when other ShareWAF starts.

Verify:

When you view the data in mongodb, you will see that there is already configuration information data in the database:

In the current version, the ability to empty mongodb database configuration information is not provided. To clear it, use the command: db.sharewaf_config.drop () in mongo.

3. Users register independently, add or delete through the administrator background, and the configuration information will be synchronized with the remote database.

4. Content that is not currently synchronized with the remote database.

Manage data detection in the background:

The data here is for individual machines that deploy ShareWAF.

The database backup and backup audit log in the background of the administrator are aimed at the sqlite database and stand-alone audit log in the independent ShareWAF machine.