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. Every verification returns its level:
  • hopae_loa: the level, from 1 to 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 connection determined the level for this verification. Absent when the level comes from the connection’s defaults.

Levels

How a level is decided

The framework scores an eID on two independent questions, each on its own scale. Identity proofing (P): how carefully was the person checked? Authentication (A): how securely does the person sign in? The two combine into one level, and the weaker of the two decides it: a government-verified person behind a single SMS code, or a hardware key on an unverified account, does not score high. The top level needs a thoroughly checked person and a login only they can perform. The framework document places these eIDs on its map: Every connection lists the levels it can reach as credential.loa[] in Get Connections and in the Console’s Connections table.
When a connection lists more than one level, such as iDIN or Evrotrust, the level depends on how the user’s identity was created with the provider. For example, iDIN is LoA 4 when the user signs in with itsme and LoA 3 with any other bank. To require a minimum, check the level after the verification. See Check the achieved LoA.

Request a target LoA

On a connection that supports it, you can ask for a level when you start a verification. The provider asks the user to sign in at that level, so hopae_loa is at least the level you request. REST and OIDC apply the same rule.
This example requests LoA 3 on cz-mojeid (MojeID CZ), which reaches levels 3 and 4.
1

Find a connection that accepts the level

Call Get Connections with your workflowId and status=enabled:
The response, trimmed to the fields this step uses:
Use a connection with acceptsRequestedLoa: true whose highest credential.loa level is at least the level you request. cz-mojeid reaches 4, so it accepts 3.
2

Create the verification with requestedLoa

Send requestedLoa to Create Verification. cz-mojeid runs a redirect flow, so redirectUri is also required:
Send the user to flowDetails.authorizationUrl. A connection that doesn’t support the level, such as smart-id, returns 422 VALIDATION_UNPROCESSABLE, and no session starts.
3

Read the achieved LoA

After the verification completes, call Get Verification Userinfo:
hopae_loa is at least requestedLoa.
Only connections with acceptsRequestedLoa: true take a requested level, even if another connection’s credential.loa includes it. To offer only connections that reach a level, enable only those connections in the workflow.

Check the achieved LoA

The verification completes whatever level it reaches: the level is returned in hopae_loa, and no error is reported for a shortfall. To require a minimum, check the level after the verification in one of two ways:
  • In your own code. Read hopae_loa from the ID token or the userinfo response on your server, and reject the user when it is below your minimum.
  • With a workflow node. On the workflow’s Flow tab, add a check-min-loa node after the verification step:
    The userinfo response then carries metLoa: true when hopae_loa is at least minLoa. The node does not block or fail the verification, and metLoa is not in the ID token. Reject the user in your own system when it is false. See Workflow Nodes.

Response example

LoA fields are included in both the ID token and the userinfo response:
Always validate hopae_loa server-side before granting access to sensitive operations.

See also