de22af0048
LoginSucceededEvent fires from NewUserAuthTokenResponse (the chokepoint where local, LDAP and OIDC logins converge), LoginFailedEvent from handleFailedPassword on every failed password check, LogoutEvent from the logout handler, and APIToken issued/revoked/used events from the token model and auth middleware. The token events carry IDs only since the freshly created token struct holds the raw token string and the poison queue logs message payloads. None of these events have a listener yet — the audit registration adds them. Dispatching to a topic without subscribers is a no-op. |
||
|---|---|---|
| .. | ||
| api | ||
| caldav | ||
| feeds | ||
| middleware | ||
| admin_gate.go | ||
| api_tokens.go | ||
| error_handler.go | ||
| feature_gate.go | ||
| healthcheck.go | ||
| metrics.go | ||
| rate_limit.go | ||
| resolve_project.go | ||
| routes.go | ||
| sentry_middleware.go | ||
| static.go | ||
| validation.go | ||