You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Feature/Enhancement:
Currently there is no log output for successful or unsuccessful login attempts. Ideally they'd be present, and include timestamp, username, ip address, X-Forwarded-For.
Why would this be helpful?:
Use case is parsing logs in elastic/logstash/kibana/beats to generate notifications for login attempts.
Future Implementation:
{timestamp} WARN: [AuthService] Failed login attempt for user {username} from ip address {ip address} (Reason: wrong password)
The text was updated successfully, but these errors were encountered:
There is. You can filter the access log by the 401 status code. Gotify logs this to stdout.
2024-05-20T18:13:17+02:00 | 401 | 300.313µs | 127.0.0.1 | POST "/client"
Error #01: you need to provide a valid access token or user credentials to access this api
2024-05-20T18:14:17+02:00 | 401 | 168.481µs | ::1 | POST "/message"
Error #01: you need to provide a valid access token or user credentials to access this api
In most cases there isn't a username, so logging it doesn't really make sense.
Type of Enhancement:
Server Backend
Describe the Feature/Enhancement:
Currently there is no log output for successful or unsuccessful login attempts. Ideally they'd be present, and include timestamp, username, ip address, X-Forwarded-For.
Why would this be helpful?:
Use case is parsing logs in elastic/logstash/kibana/beats to generate notifications for login attempts.
Future Implementation:
{timestamp} WARN: [AuthService] Failed login attempt for user {username} from ip address {ip address} (Reason: wrong password)
The text was updated successfully, but these errors were encountered: