# `Ithibati.Credo.NoWaxConfiguration`
[🔗](https://github.com/oliverandrich/ithibati/blob/v0.6.2/lib/ithibati/credo/no_wax_configuration.ex#L4)

## Basics

> #### This check is disabled by default. {: .neutral}
>
> [Learn how to enable it](`e:credo:config_file.html#checks`) via `.credo.exs`.

This check has a base priority of `high` and works with any version of Elixir.

## Explanation

`config :wax_, rp_id:` and `origin:` configure nothing that Ithibati does.

`wax_` reads them as its own defaults, and Ithibati never lets them be reached. It passes
both on every call, so one application can serve a browser and a native client with
different answers. What you set here is not what a ceremony uses. This is also exactly
where somebody looks for the setting, which is why it is worth a warning rather than
silence.

Ithibati passes the relying party and the origin per call instead. The routes derive them
from your endpoint's configured `:url`, and `c:Ithibati.Web.Handler.relying_party/2` is
where an application answers differently for a client whose origin is not that URL.

This check reads `config/*.exs`, which Credo does not include by default. Add `config/`
to `files.included` in your `.credo.exs`, or the check has nothing to look at.

## Check-Specific Parameters

*There are no specific parameters for this check.*

## General Parameters

Like with all checks, [general params](`e:credo:check_params.html`) can be applied.

Parameters can be configured via the [`.credo.exs` config file](`e:credo:config_file.html`).

---

*Consult [api-reference.md](api-reference.md) for complete listing*