[Feature Request] Log authentication failures to systemd-journald

[micush]

Hi Shreyas,

I hope this finds you well. If possible, can you log authentication failures to systemd-journald? This will allow people to configure things like fail2ban to use the systemd service logs for the dns service to protect the web interface from password spraying. I know you already have such an internal device for this type of prevention, but it appears to not be configurable, does not appear to log failures that I can see, and does not prevent access to the web interface itself after the authentication limit is reached.

I know somebody already asked for more homogeneous naming of the log files to more easily enable fail2ban and you already said no to that because the application log file format can change and break the integration, but if you send authentication failure log messages to systemd-journald like you do the service startup messages these should be safe from application log file changes and allow us to monitor the service messages for authentication failures and run whatever applications we want to based on the authentication failure messages in the service log.

It's how Proxmox is doing it with their products and it works quite well with fail2ban and similar apps, all while not affecting the specific application log file format. It would certainly help me out with authentication failure containment, analysis, and reporting.

As always, thanks a lot for such a wonderful product.

micush

[ShreyasZare]

Thanks for the post and compliments. Will see how this can be implemented.

[micush]

Thanks a lot. I appreciate it.