Event type
Auth0 wrong-password authentication
Auth0 database authentication failure caused by a wrong password; registry identities and application, fresh UTC time and synthetic log identifiers.
Overview
What this event covers
One documented fp scenario, with required registry fixture relationships. Requires source-specific entities: entities/okta/auth0/authentication.yaml; example configuration: configs/okta/auth0/authentication.yaml. Tested with MELTr rc3 commit 1e14e5defb66f6ac24decbe59c1c4f4e64877618. Entity fixtures must be selected per source; generic registry preview entities are not sufficient.
When generated
- ›A known database user supplies an incorrect password.
Security relevance
InformationalFrequency notes
Local test rate of 3600 events/hour. Example generator stops after five events.
Resources
Docs and tools
Generation
Configuration
- Base frequency
- 3600 events/hour
- Business hours
- 1.0x
- Night hours
- 1.0x
- Weekend
- 1.0x
Schema
Field definitions
Field reference for this event type — types, requirements, examples, and allowed values.
date
Jinja: one `now()` value, serialized with MELTr `iso8601_utc` and sliced to milliseconds Fresh UTC ISO timestamp with milliseconds; test clock injection is confined to validation.
Source: Jinja: one `now()` value, serialized with MELTr `iso8601_utc` and sliced to milliseconds Fresh UTC ISO timestamp with milliseconds; test clock injection is confined to validation.
2026-10-01T22:48:18.924Ztype
Fixed `fp` Only the documented wrong-password branch.
Source: Fixed `fp` Only the documented wrong-password branch.
fpdescription
Fixed `Wrong email or password.` Same message as details.error.message.
Source: Fixed `Wrong email or password.` Same message as details.error.message.
Wrong email or password.connection
Fixed `Username-Password-Authentication` One database connection in this profile.
Source: Fixed `Username-Password-Authentication` One database connection in this profile.
Username-Password-Authenticationconnection_id
Fixed `con_ExampleLab01` Synthetic fixture identity for that connection.
Source: Fixed `con_ExampleLab01` Synthetic fixture identity for that connection.
con_ExampleLab01client_id
Registry: named service.service_id Stable per application; local alphanumeric/underscore/hyphen constraint.
Source: Registry: named service.service_id Stable per application; local alphanumeric/underscore/hyphen constraint.
ExampleLabClient01client_name
Registry: same service.description Nonempty display name; JSON escaping preserves special characters.
Source: Registry: same service.description Nonempty display name; JSON escaping preserves special characters.
Example Customer Portalip
Registry: selected user’s named browser device.ip_address IPv4; fixtures use documentation addresses.
Source: Registry: selected user’s named browser device.ip_address IPv4; fixtures use documentation addresses.
192.0.2.21user_agent
Fixed documented Chrome/macOS string Historical profile, not a current-browser claim; fixture device must match.
Source: Fixed documented Chrome/macOS string Historical profile, not a current-browser claim; fixture device must match.
Chrome 86.0.4240 / Mac OS X 10.15.6details
Jinja dictionary Contains only error for this scenario.
Source: Jinja dictionary Contains only error for this scenario.
{"error":{"message":"Wrong email or password."}}details.error
Jinja dictionary Contains only message for this scenario.
Source: Jinja dictionary Contains only message for this scenario.
{"message":"Wrong email or password."}details.error.message
Fixed wrong-password message Agrees with description.
Source: Fixed wrong-password message Agrees with description.
Wrong email or password.user_id
Jinja: `auth0|` plus registry user.user_id Stable across events for the selected user; synthetic mapping, not a provisioned Auth0 account.
Source: Jinja: `auth0|` plus registry user.user_id Stable across events for the selected user; synthetic mapping, not a provisioned Auth0 account.
auth0|37f967cdbf8ebf2727378558user_name
Registry: same user.email MELTr-valid email; no example.com-only restriction.
Source: Registry: same user.email MELTr-valid email; no example.com-only restriction.
ben.rivera@example.comstrategy
Fixed `auth0` Database connection profile.
Source: Fixed `auth0` Database connection profile.
auth0strategy_type
Fixed `database` Paired with strategy and connection.
Source: Fixed `database` Paired with strategy and connection.
databaselog_id
Faker: `fake.numerify`, one call/event 57-digit synthetic value starting with 9; local test representation, not Auth0’s ID algorithm. Randomness is not a global uniqueness guarantee.
Source: Faker: `fake.numerify`, one call/event 57-digit synthetic value starting with 9; local test representation, not Auth0’s ID algorithm. Randomness is not a global uniqueness guarantee.
976779132038249620293929323493172846334245207770795734897_id
Reuse event log_id Identical to log_id; included only because the reference example includes it.
Source: Reuse event log_id Identical to log_id; included only because the reference example includes it.
976779132038249620293929323493172846334245207770795734897isMobile
Fixed Jinja `false` Desktop browser profile; emitted as a JSON boolean.
Source: Fixed Jinja `false` Desktop browser profile; emitted as a JSON boolean.
false