Skip to main content

Overview

Hopae scores assurance on one comparable scale: the Hopae Level of Assurance (HLoA), from 1 to 4, defined by the Hopae Global Assurance Framework. It is built on the NIST and eIDAS standards and calibrated so that HLoA 4 equals eIDAS High. Hopae returns three fields:
  • hopae_loa — the level, 1–4, for programmatic checks
  • hopae_loa_label — the level’s label (none, low, substantial, high)
  • acr — the urn:hopae:loa:{level} URN, present when the provider determined the level

LoA levels

The framework scores each eID on two independent axes, identity proofing (how carefully the person was checked) and authentication (how securely they sign in), and the weaker of the two decides the level. See the framework document for the scales and the eID map.

Specify LoA in requests

Request a minimum LoA when initiating verification:
Add acr_values query parameter:
See acr_values format for additional options including provider filtering.
When not specified, the provider’s minimum supported LoA is used. Hopae passes the requested level on to the provider only for MojeID. Other providers are asked for a fixed level, or for none, so the level depends on the user’s account at the provider. When it is below the requested level, the verification ends failed (see Error handling).

Error handling

Provider does not support the requested LoA Returns an error before authentication begins:
  • OIDC: Error callback redirect
  • REST API: HTTP 422
If the final LoA is lower than requested This can occur when:
  • The user chooses a weaker authentication method than expected
  • The provider downgrades the session due to fallback mechanisms
The verification status becomes failed, but you can still retrieve user data via the /userinfo endpoint. This allows you to decide how to handle the situation

Response example

LoA fields are included in both ID Token and UserInfo responses:
Always validate hopae_loa server-side before granting access to sensitive operations.

See also