PDFlibPas: compliance and signing workbench in Delphi

losLab PDF Library ger Delphi- och C++Builder-team en PDF-motor med tillgänglig källkod för skrivbord, server, DLL, ActiveX och Dylib, med inbyggda PDF/A- och PDF/UA-kontroller, PAdES-signering och valbara renderare utan extern PDF-tjänst.

Den här artikeln är skriven för teams combining validation, remediation, signature preparation, and evidence review in one Delphi workflow. Den behandlar compliance and signing workbench som produktionsnära dokumentteknik, inte som ett isolerat komponentanrop.

Den praktiska risken är att separate validation and signing tools can disagree about the document state, leaving operators unsure which revision was checked and which revision was signed. Därför behöver flödet ett skrivet kontrakt, observerbar diagnostik och realistiska regressionsfiler.

Arkitekturbeslut

Use one workbench record for the document lifecycle. validation profiles required before signing and after signing / remediation actions allowed inside the workbench versus upstream templates

validation profiles required before signing and after signing
remediation actions allowed inside the workbench versus upstream templates
certificate source, timestamp authority, revocation source, and operator roles
waiver workflow for compliance warnings that do not block signing

Implementeringsflöde

Validate before the signing revision is created. Ordningen nedan gör arbetsflödet granskbart för Delphi- och C++Builder-team.

create a workbench record and hash the source file before analysis
run compliance validation and classify findings into fix, waive, or block
apply approved remediation before the signature field is reserved
sign the validated revision and immediately run post-sign validation
package reports, hashes, certificate data, and operator decisions together

Valideringsbevis

Workbench evidence that survives audit. Behåll dessa fält tillsammans med utdata eller supportunderlaget.

source hash, validation profile, issue summary, remediation list, and waiver list
certificate fingerprint, timestamp result, revocation status, and signer identity
pre-sign and post-sign validation reports with matching document references
final file hash and workbench decision trail

Validation and signing must agree on bytes

A compliance and signing workbench should tie the input hash, validation profile, remediation decisions, signing certificate, timestamp, and final validation result together. Without that chain, a signed file can be difficult to explain later.

Operational metrics to watch

The first release should expose enough metrics to prove the workflow is healthy under real files, not only under curated samples.

count and rate for source hash, validation profile, issue summary, remediation list, and waiver list
warning trend for fixing compliance issues after signing changes the revision that was trusted
latency of the stage that must create a workbench record and hash the source file before analysis
profile usage for validation profiles required before signing and after signing

Tekniska granskningsnoteringar för compliance and signing workbench

Använd dessa granskningsnoteringar för att säkerställa att funktionen har passerat demo-nivån och kan försvaras under leverans, support och kundeskalering.

Beslut: validation profiles required before signing and after signing. Implementeringspresspunkt: run compliance validation and classify findings into fix, waive, or block. Acceptansbevis: pre-sign and post-sign validation reports with matching document references. Regressionsutlösare: operators need a clear blocked state when the source cannot be trusted
Beslut: remediation actions allowed inside the workbench versus upstream templates. Implementeringspresspunkt: apply approved remediation before the signature field is reserved. Acceptansbevis: final file hash and workbench decision trail. Regressionsutlösare: fixing compliance issues after signing changes the revision that was trusted
Beslut: certificate source, timestamp authority, revocation source, and operator roles. Implementeringspresspunkt: sign the validated revision and immediately run post-sign validation. Acceptansbevis: source hash, validation profile, issue summary, remediation list, and waiver list. Regressionsutlösare: waivers should identify an owner and expiry rather than becoming permanent silence
Beslut: waiver workflow for compliance warnings that do not block signing. Implementeringspresspunkt: package reports, hashes, certificate data, and operator decisions together. Acceptansbevis: certificate fingerprint, timestamp result, revocation status, and signer identity. Regressionsutlösare: timestamp services and validators may fail independently of PDF generation

Gränsfall

fixing compliance issues after signing changes the revision that was trusted
waivers should identify an owner and expiry rather than becoming permanent silence
timestamp services and validators may fail independently of PDF generation
operators need a clear blocked state when the source cannot be trusted

Delphi / C++Builder notes

PDFlibPas should sit behind a small service boundary that receives files, streams, profiles, and credentials, then returns output paths, warnings, metrics, and validation status. Important terms include compliance, PAdES, preflight, timestamp, waiver, validation report.

Delphi-kodexempel

Följande Delphi-skiss visar en praktisk servicegräns för detta ämne. Håll policykontroller, loggning och validering utanför det smala produktanropet så att arbetsflödet går att testa.

procedure RunComplianceSigningJob(const InputFile, OutputFile: string; const Policy: TSigningPolicy);
var
  Pdf: TPDFlib;
begin
  Pdf := TPDFlib.Create;
  try
    Pdf.LoadFromFile(InputFile, Policy.OpenPassword);
    PrepareComplianceEvidence(Pdf, Policy);
    CompleteSigningWorkflow(Pdf, OutputFile, Policy);
    ValidateSignedOutput(OutputFile, Policy.ProfileName);
  finally
    Pdf.Free;
  end;
end;

Produktionschecklista

Kör arbetsflödet på en tom fil, en normal kundfil och en värstafallfil
Öppna den genererade PDF-filen med rätt visare, validator, skrivare eller nedströmsapplikation
Logga produktversion, profilversion, inmatningshash, utdatasökväg, förfluten tid och antal varningar
Håll lösenord, certifikat, tillfälliga filer och kunddata under tydliga lagringsregler
Lägg till regressionsdokument när en kundfil avslöjar ett nytt gränsfall

Produktdokumentation

PDFlibPas

Fler kodexempel

ProcessID := PDF.NewSignProcessFromFile('invoice-fixed.pdf', '');
if ProcessID = 0 then
  raise Exception.Create('Cannot open source for signing');
PDF.SetSignProcessField(ProcessID, 'ApprovalSig');
PDF.SetSignProcessPFXFromFile(ProcessID, 'company.pfx', PfxPassword);
PDF.SetSignProcessInfo(ProcessID, 'Invoice approval', 'Berlin', 'billing@example.com');
PDF.SetSignProcessCustomSubFilter(ProcessID, 'ETSI.CAdES.detached');  // PAdES baseline
PDF.SetSignProcessDigestAlgorithm(ProcessID, 2);                      // SHA-256
PDF.SetSignProcessReserveContentsBytes(ProcessID, 8192);              // room for a later timestamp
PDF.EndSignProcessToFile(ProcessID, 'invoice-signed.pdf');
if PDF.GetSignProcessResult(ProcessID) <> 1 then
  Writeln('Sign failed, code ', PDF.GetSignProcessResult(ProcessID));
PDF.ReleaseSignProcess(ProcessID);

var
  Doc: TPDFlibSignDoc;
  Names: TStringList;
  FS: TFileStream;
  I: Integer;
  SourceSize, RangeStart, GapStart, TailStart, TailLen: Int64;
begin
  // Capture the size before Open: the audit object holds a share lock on the file
  FS := TFileStream.Create('invoice-signed.pdf', fmOpenRead or fmShareDenyNone);
  SourceSize := FS.Size;
  FS.Free;
  Doc := TPDFlibSignDoc.Create;
  Names := TStringList.Create;
  try
    if not Doc.Open('invoice-signed.pdf', '', False) then Exit;
    Doc.GetSignatureFieldNames(Names);
    for I := 0 to Names.Count - 1 do
      if Doc.GetSignatureValueObjNum(Names[I]) > 0 then  // > 0 means the field is signed
      begin
        RangeStart := StrToInt64(string(Doc.GetSignatureValueByName(Names[I], 11)));
        GapStart   := StrToInt64(string(Doc.GetSignatureValueByName(Names[I], 12)));
        TailStart  := StrToInt64(string(Doc.GetSignatureValueByName(Names[I], 13)));
        TailLen    := StrToInt64(string(Doc.GetSignatureValueByName(Names[I], 14)));
        if (RangeStart = 0) and (TailStart + TailLen = SourceSize) then
          Writeln(Names[I], ': signature covers the file to EOF')
        else
          Writeln(Names[I], ': earlier revision, or unusual ByteRange layout');
      end;
    Doc.Close;
  finally
    Names.Free;
    Doc.Free;
  end;
end;