MishkaCmsCore.Accounts.RecoveryCode (Mishka CMS Core v0.0.1)

An account's one-time recovery codes, for signing in when its authenticator app is lost — the store of AshAuthentication's recovery_code strategy on MishkaCmsCore.Accounts.User. See MishkaCmsCore.Accounts.SecondFactor.

Only a hash of each code is kept; the codes themselves are shown once, when they are made. A code that signs someone in is deleted. Like MishkaCmsCore.Accounts.Token, a row is reached through its account and never by site: the strategy's own reads and deletes carry AshAuthentication's context, and otherwise an account reaches only its own.

Summary

Types

t()

Functions

default_short_name()

input(opts)

Validates that the keys in the provided input are valid for at least one action on the resource.

input(opts, action)

Same as input/1, except restricts the keys to values accepted by the action provided.

primary_key_matches?(left, right)

Types

t()

@type t() :: %MishkaCmsCore.Accounts.RecoveryCode{
  __lateral_join_source__: term(),
  __meta__: term(),
  __metadata__: term(),
  __order__: term(),
  aggregates: term(),
  calculations: term(),
  code: term(),
  id: term(),
  inserted_at: term(),
  user: term(),
  user_id: term()
}

Functions

default_short_name()

input(opts)

@spec input(values :: map() | Keyword.t()) :: map() | no_return()

Validates that the keys in the provided input are valid for at least one action on the resource.

Raises a KeyError error at compile time if not. This exists because generally a struct should only ever be created by Ash as a result of a successful action. You should not be creating records manually in code, e.g %MyResource{value: 1, value: 2}. Generally that is fine, but often with embedded resources it is nice to be able to validate the keys that are being provided, e.g

Resource
|> Ash.Changeset.for_create(:create, %{embedded: EmbeddedResource.input(foo: 1, bar: 2)})
|> Ash.create()

input(opts, action)

@spec input(values :: map() | Keyword.t(), action :: atom()) :: map() | no_return()

Same as input/1, except restricts the keys to values accepted by the action provided.

primary_key_matches?(left, right)