MPL - com.phenixidentity~phenix-store-mpl
MPL module, com.phenixidentity~phenix-store-mpl, is responsible for serving and persisting data tied to users. This would be tokens, lockouts etc. IE non config data.
By default events are also stored within the mpl module.
Configuration parameters
| Key | default value |
Description |
|---|---|---|
| password | N/A | Password used to connect to database. |
| user |
N/A | User used to connect to database. |
| encryption.key |
N/A | used when encrypting data in the database |
| export_start |
01:00 | When to start data export/backup. Use HH:MM format. |
| driver_class |
N/A | JDBC v4 driver class |
| dataretention |
60 | Number of days entries will stay in the database before deleted |
| is_server |
true | Should PAS be database server or just act as a client using external databse |
| url |
N/A | JDBC connection URL. |
Default configuration
"config": {
"password": "<the_password_set_at_installation>",
"user": "PhenixidID2014!",
"encryption.key": "<the_key_set_at_installation>",
"export_start": "15:00",
"driver_class": "org.hsqldb.jdbc.JDBCDriver",
"dataretention": "60",
"is_server": "true",
"url": "jdbc:hsqldb:hsql://localhost:9001/phenixid"
}
Click to copy
Data retention
Entries in the database holding a value in the expires column or is an event will be subject of automatic removal. The number of days data is retained after expire is controlled by the dataretention key.
Note that the automatic deletion of data is only performed when acting as a server.
Automatic backup
Data is backed up once a day. Backups are stored in "data/backup/". Administrators can control the time of data being backed up using the export_start configuration key.
Backups are only performed when acting as a server.