Skip to content

Update 2-implement.md #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renejeglinsky wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update 2-implement.md #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions documentation/auditlog/2-implement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ The steps above is all you need to automatically log personal data-related event


## Adding Custom Audit Logs
As part of audit logs, there can be cases where you want to genereate custom audit logs. For example if you want to log 403 - Forbidden events when an user is not having roles but is still trying to access certain data.
As part of audit logs, there can be cases where you want to generate custom audit logs. For example if you want to log 403 - Forbidden events when a user is not having roles but is still trying to access certain data.
This can be achieved by adding custom handlers in a CAP application.


Expand Down Expand Up @@ -232,4 +232,4 @@ Run the request to read all Customers. In the Console log you see output like th
time: 2024-11-04T05:10:38.441Z
}
```
Here our custom handler is generating these custom `security-events`.
Here our custom handler is generating these custom `security-events`.