Adjust the verifier configuration

Beyond its identity, the verifier has three behaviour settings: request-object signing, session lifetime and identity reconciliation. This journey reads all three and then adjusts each one.

Complete first: Set up the verifier.

Steps and why they come in this order

Step	Why here
1. Read the current settings	See how requests are signed, how long sessions last and whether reconciliation is enforced before changing any of it.
2. Configure request-object signing	Wallets authenticate the verifier by the request-object signature. The signing identity must match what wallets and trust lists expect.
3. Set the session lifetime	The session TTL bounds how long a wallet has to respond and how long a result can be polled.
4. Configure identity reconciliation	Reconciliation decides whether a presentation must map to a known user. It is last because it depends on the claims your queries request.

All three settings are merge-patch resources: absent fields stay unchanged and an explicit null clears one. They apply to every request the verifier creates from then on; requests already created keep the values they were created with.

Deeper reference

The console shows these as Protocols > Verifier > Settings tabs: Request object signing, Sessions and Reconciliation.

Next journey

Continue with Author DCQL queries.