Loading
Fix omniauth_login_failed audit event streaming
What does this MR do and why?
Fix omniauth_login_failed audit event streaming by utilizing the existing UnauthenticatedSecurityEventAuditor with some changes. Previously, events were not streaming because of a nil entity and would have also been dropped because determine_audit_model_entity/determine_from_entity_type would fail to do a user lookup.
References
Screenshots or screen recordings
| Before | After |
|---|---|
![]() |
![]() |
omniauth_login_failed
| Before | After | |
|---|---|---|
| API - Non-existing user |
|
|
| Stream - Non-existing user | None |
|
| API Existing user |
|
|
| Stream - Existing user | None |
|
login_failed_with_standard_authentication (control - unchanged)
| Before | After | |
|---|---|---|
| API - Non-existing user |
|
|
| Stream - Non-existing user |
|
|
| API - Existing user |
|
|
| Stream - Existing user |
|
|
How to set up and validate locally
- Enable LDAP
- Add a new HTTP destination
- In a private browser, initiate a failed LDAP login
- Observe that:
- DB Audit events capture the event successfully
- Streaming destinations now receive the event, previously they did not.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #618809 (closed)
Edited by Jio Castillo

