Wallet Sdk Options
Configuration options for bootstrapping the EUDI wallet and document manager.
The hosting app decides:
which issuer / client ID to use (issuerUrl, clientId),
which verifiers are preregistered (verifiers),
how the local DB is named (dbFileName),
how keys are created in Android Keystore (useStrongBoxForKeys, userAuthenticationRequired, userAuthenticationTimeoutMillis).
This keeps "environments" (staging/prod/etc.) as an app-level concern.
Constructors
Properties
OpenID4VCI authorization-code redirect URI.
Name of the file where the wallet DB will be stored, under context.noBackupFilesDir.
Allow-list of expected app signing-certificate SHA-256 hashes (:/space-separated and case-insensitive accepted). Used by the device-integrity capture (gated by a verifier's transaction_data) to evaluate the repackaging signal. When empty (the default), repackaging is reported as INCONCLUSIVE and only the observed signing hashes are surfaced for out-of-band comparison by the backend/PSP.
Whether Pushed Authorization Requests (PAR) are mandatory for issuance.
Secure area implementation identifier used for document keys.
Optional sink for wallet transaction events (issuance, presentation, signing, deletion).
Trusted VCT metadata registries used by the SDK when enriching com.dewa.walletsdk.api.IssuedDocumentHandle instances.
Whether keys should be bound to explicit user authentication (PIN/biometric) before usage.
How long (in milliseconds) the user authentication should remain valid for key usage, when userAuthenticationRequired is true.
Whether to request StrongBox-backed keys when available.
Preregistered verifiers the wallet should trust for OpenID4VP.