THPDFSignatureProviderRequest Record
Carries the algorithm, input, key material and bookkeeping identifiers for one signature provider operation
Declaration
THPDFSignatureProviderRequest= record
Algorithm: THPDFSignatureAlgorithm;
AlgorithmOID: AnsiString;
DigestAlgorithmOID: AnsiString;
PSSSaltLength: Integer;
InputKind: THPDFSignatureInputKind;
Input: TBytes;
PublicKey: TBytes;
Signature: TBytes;
CertificateDER: TBytes;
KeyIdentifier: AnsiString;
OperationIdentifier: AnsiString;
Context: TBytes;
end;
Unit
HPDFSignatureProvider
Fields
| Field | Purpose |
|---|---|
Algorithm | Signature algorithm to carry out, such as hsaRSAPKCS1v15, hsaRSAPSS or hsaECDSA |
AlgorithmOID | Object identifier naming the signature algorithm |
DigestAlgorithmOID | Object identifier naming the digest algorithm |
PSSSaltLength | Salt length for RSA-PSS; the provider rejects values outside 0..65535 |
InputKind | Whether Input holds a message (sikMessage) or a digest that is ready to use (sikDigest) |
Input | Message or digest bytes; input that is empty or oversized is rejected as malformed |
PublicKey | Public key bytes brought in when a signature is verified |
Signature | Signature bytes that verify operations check |
CertificateDER | DER certificate used for estimating the resulting signature size |
KeyIdentifier | Provider-specific identifier that names the signing key |
OperationIdentifier | Identifier that the provider checks against its cancellation source between retries |
Context | Provider-defined context bytes that travel with the request |
Usage notes
- Passed to the
Sign,VerifyandEstimateSignatureSizemembers ofTHPDFSignatureProviderimplementations - Providers validate
InputKindand theInputlength first, returningspsMalformedwhen they disagree withAlgorithm - Custom transports receive the same record plus the retry attempt number and may look at
OperationIdentifierfor cancellation