A cryptographically valid PDF signature is not automatically a Qualified Electronic Signature (QES).
Technical signature validation answers questions such as:
- Is the CMS/PAdES signature cryptographically valid?
- Is the certificate chain valid?
- Is the certificate revoked?
- Is the RFC 3161 timestamp valid?
- Does the document satisfy PAdES B-B, B-T, B-LT or B-LTA requirements?
eIDAS qualification requires another layer of trust evidence.
PL/SIGN now combines its existing PAdES/CAdES validation engine with Trusted List and certificate qualification processing.
The new eIDAS layer supports:
- EU LOTL and national Trusted List processing
- binding the signer certificate to the exact Trusted List service through RFC 5280 certificate-path validation
- ETSI qualification and qualifier rules, including QCWithQSCD, QCNoQSCD, QCForESig and QCForESeal
- QCStatements and QSCD evaluation
- QES and qualified electronic seal classification
- historical service-state evaluation
- trusted signing time derived from validated RFC 3161 signature timestamps
- Trusted List edition, sequence, validity and SHA-256 binding
A key design principle is fail-closed validation.
Missing trust evidence, unknown service states or incomplete validation data cannot silently become a QES result. Where the available evidence is insufficient, PL/SIGN returns an indeterminate result instead.
Trusted List authenticity is also bound to the exact XML content. A simple "VERIFIED" flag is not treated as proof. Verified LOTL and national Trusted List evidence is represented by opaque handles tied to the exact SHA-256 digest and edition metadata, preventing a verified result for one Trusted List from being reused with another.
For remote signing, PL/SIGN works together with PL_SIGN_CSC, the generic CSC-based remote signing layer. This allows the same architecture to work with compatible European QTSPs while keeping provider-specific logic outside the signature engine.
Supported cryptographic profiles include RSA PKCS#1, RSA-PSS and ECDSA with SHA-256, SHA-384 and SHA-512.
The important part for Oracle developers: the signature, PDF, PKI and eIDAS qualification logic runs directly inside the database in PL/SQL.
No separate Java application is required for the core document-signing and validation pipeline.
PL/SIGN: database-native digital signatures, PAdES and eIDAS trust processing for Oracle.
