BruteForceAccountResolution
How one requested account filter name was resolved through the account mappings Nauthilus stores when a backend finds a login name. A mapping is not re-verified against the backend and can be stale; a name that was never used for a login has no mapping. The literal name is always checked as well.
mapped: exactly one stored account. unmapped: no stored account, only the literal name was checked. ambiguous: several stored accounts, all were checked. error: the stored accounts could not be read, the result is undecided and the listing reports an error.
Possible values: [mapped, unmapped, ambiguous, error]
Resolver that produced accounts, currently account_mapping.
Names tested against the affected-account state, the input first.
Checked names that currently have affected-account state, before paging.
{
"input": "string",
"status": "mapped",
"source": "string",
"accounts": [
"string"
],
"checked": [
"string"
],
"matched": [
"string"
],
"literal_match": true,
"error": "string"
}