Read device policy configuration
Reads the device policy configuration of the wallet provider of the individual wallet units: the device rules on Android. The configuration has the minimum Android version (`minimumAndroidVersion`). The key origin rule is always on, so it has no member. There is one device policy configuration for each wallet provider, so the path has no id. A new configuration has no minimum Android version.
Update device policy configuration
Replaces the device policy configuration of the wallet provider of the individual wallet units: the device rules on Android. Send `minimumAndroidVersion` (9 to 99), or `null` for no minimum. The key origin rule is always on, so it has no member.
List vulnerable device classes
Lists the vulnerable device classes of the device policy, newest first, one page at a time. The wallet provider refuses an Android device whose model (`X-Wallet-Device-Model`) and attested Android version are in a class (reason `device_class_vulnerable`). The device policy applies to the Android requests: the registration of a wallet unit, each Wallet Unit Attestation request and each key attestation request. A refused request gets `403` with `individual_wallet_unit.device_refused`.
Create vulnerable device class
Adds a vulnerable device class: an Android device model, with all its Android versions or only some. `createdBy` is the caller. The device policy applies to the Android requests: the registration of a wallet unit, each Wallet Unit Attestation request and each key attestation request. A refused request gets `403` with `individual_wallet_unit.device_refused`. To revoke the wallet units that are registered on such devices already, run [Scan device policy](/docs/openid4vc-api/config-scan-digital-wallet-open-id-device- policy).
Delete vulnerable device class
Deletes a vulnerable device class. The wallet provider then accepts the devices of the class again. A wallet unit that a scan revoked stays revoked.
List leaked attestation keys
Lists the leaked attestation keys of the device policy, newest first, one page at a time. The wallet provider refuses an Android Key Attestation chain that has a certificate with one of these SHA-256 fingerprints (reason `attestation_key_leaked`). The device policy applies to the Android requests: the registration of a wallet unit, each Wallet Unit Attestation request and each key attestation request. A refused request gets `403` with `individual_wallet_unit.device_refused`.
Create leaked attestation key
Adds a leaked attestation key: the SHA-256 fingerprint of a certificate of an Android Key Attestation chain whose private key is known to be leaked. `createdBy` is the caller. The device policy applies to the Android requests: the registration of a wallet unit, each Wallet Unit Attestation request and each key attestation request. A refused request gets `403` with `individual_wallet_unit.device_refused`. To revoke the wallet units that are registered with such a chain already, run [Scan device policy](/docs/openid4vc-api/config-scan-digital-wallet-open-id- device-policy).
Delete leaked attestation key
Deletes a leaked attestation key. The wallet provider then accepts the key attestation chains with this certificate again. A wallet unit that a scan revoked stays revoked.
Scan device policy
Checks the stored Android wallet units against the device policy: the units that are not deleted and not revoked, with the device data that their requests stored (the device model, the key attestation chain, and the latest attested security patch level and Android version). The scan applies the vulnerable device classes, the leaked attestation keys, and the device rules of the device policy configuration. A wallet unit that no rule matched and that has no stored device data that the rules need is counted in `unknownDevice`.