Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
When the graphomate server is accessed for the first time it will create a folder called graphomate at the tomcat root folder with initial content. In this folder a file called auditing.db will be created which contains the data for the audits. Besides there will be three two subfolders. The templates folder where templates will will be stored, the rulesets folder where rulesets will be stored and stored and the config folder where two .ini-files will be created.
access.ini
Code Block | ||||
---|---|---|---|---|
| ||||
protected=true username=admin password=graphomate |
The parameter protected defines if the admin should be protected by username and password. Set to false to deactivate the protection.
If set to true the admin will promt for the username and password which are definded in the parameters with the identical name.
config.ini
Code Block | ||||
---|---|---|---|---|
| ||||
[templates] allow_deletelist=true allow_create=true allow_saveupdate=true allow_listdelete=true [rulesets] allow_deletelist=true allow_create=true allow_saveupdate=true allow_listdelete=true [audits] enable=true component_white_list= |
Parameters beginning with allow_ are boolean and define if the mentioned operation will be disabled on the API of the graphomate server. The header written in square brackets define for which resource the next parameters will match.
For the auditing the enable parameter einables enables the auditing in general. It can take up to three days until the clients will check if the auditing is enabled.
The component_white_list is a list of component names or regual expressions separated by comma. If defines which components should be tracked by the standalone auditing component.
Warning |
---|
As of version 2021.4 of the graphomate server, new rulesets can no longer be created. Old rules can still be accessed. |