SupremeConfiguration
Integrated attestation configuration for the Supreme attestation verifier
This configuration deals with two aspects of integrated attestation:
Configuring attestation policies for Android and iOS.
Defining object identifiers, key constraints, proof authentication, and requested client attributes for fully integrated attestation.
To add custom Android revocation checkers, see AndroidRevocationList.loaderRegistry. To add custom time sources / clocks, see SupremeConfiguration.Clock.registry
See also
for more details on the semantics od OIDs and KeyConstraints
Constructors
iOS-Only configuration
Android-Only configuration
Types
Configures the time source of a SupremeConfiguration
Properties
Android-specific attestation configuration. For full details, see AndroidAttestationConfiguration
Object identifier for the attestation proof.
Default authentication mode placed in issued challenges. Signature mode proves private-key possession; hash mode binds the TBS CSR contents through the platform attestation nonce without signing it.
Configuration for default key constraints, such as supported cryptographic operations.
Optional object identifier for the generic device name.
iOS-specific attestation configuration. For full details, see IosAttestationConfiguration
Maximum HTTP payload size, in bytes, accepted for an attestation proof. Warden Supreme uses the same limit at the HTTP boundary for issued challenges and attestation responses. The default accommodates normal CSRs and certificate chains.
Optional ordered client-provided values to request and bind into every issued challenge.
The time offset used during attestation verification.