View Source Boruta.Config (Boruta core v3.0.0-beta.3)

Utilities to access Boruta configuration ad set defaults.

Boruta configuration can be set as following in config.exs overriding following default configuration

config :boruta, Boruta.Oauth,
  repo: MyApp.Repo, # mandatory
  cache_backend: Boruta.Cache,
  contexts: [
    access_tokens: Boruta.Ecto.AccessTokens,
    clients: Boruta.Ecto.Clients,
    codes: Boruta.Ecto.Codes,
    preauthorized_codes: Boruta.Ecto.PreauthorizedCodes,
    resource_owners: MyApp.ResourceOwners, # mandatory for user flows
    scopes: Boruta.Ecto.Scopes,
    requests: Boruta.Ecto.Requests,
    credentials: Boruta.Ecto.Credentials
  ],
  max_ttl: [
    authorization_code: 60,
    authorization_request: 60,
    access_token: 60 * 60 * 24,
    id_token: 60 * 60 * 24,
    refresh_token: 60 * 60 * 24 * 30
  ],
  ebsi_did_resolver_base_url: "https://api-conformance.ebsi.eu/did-registry/v5",
  did_resolver_base_url: "https://api.godiddy.com/1.0.0/universal-resolver",
  did_registrar_base_url: "https://api.godiddy.com/1.0.0/universal-registrar",
  universal_did_auth: %{
    type: "bearer",
    token: DID_API_KEY
  },
  token_generator: Boruta.TokenGenerator,
  issuer: "boruta"

Note: To use the did resolver and registrar services, you must provide a compliant server. Here the default is set to the Godiddy server which require an API key to perform the requests.