Fix audit events related documentation

Closes gh-8319
This commit is contained in:
Vedran Pavic 2017-02-14 23:51:53 +01:00 committed by Stephane Nicoll
parent 9e1238e286
commit 1c8f1c709c
2 changed files with 3 additions and 2 deletions

View File

@ -43,7 +43,7 @@ For Gradle, use the declaration:
delta (an increment or decrement). Metrics for all HTTP requests are automatically
recorded, so if you hit the `metrics` endpoint should see a sensible response.
* **Audit** Spring Boot Actuator has a flexible audit framework that will publish events
to an `AuditService`. Once Spring Security is in play it automatically publishes
to an `AuditEventRepository`. Once Spring Security is in play it automatically publishes
authentication events by default. This can be very useful for reporting, and also to
implement a lock-out policy based on authentication failures.
* **Process Monitoring** In Spring Boot Actuator you can find `ApplicationPidFileWriter`

View File

@ -2710,7 +2710,8 @@ to the home page at "/" and keep the default for everything else:
If the Actuator is also in use, you will find:
* The management endpoints are secure even if the application endpoints are insecure.
* Security events are transformed into `AuditEvents` and published to the `AuditService`.
* Security events are transformed into `AuditEvent` instances and published to the
`AuditEventRepository`.
* The default user will have the `ADMIN` role as well as the `USER` role.
The Actuator security features can be modified using external properties