LTV-SDO changes for Norwegian BankID third-party signing
Our Norwegian BankID third-party (PKI) signing method uses the signer's certificate to create the signature. Its method type is THIRD_PARTY (signatureMethods[].type in the REST API). The method name can be anything, but common names are nbid-sign and nbid-csc-sign. The LTV-SDO version remains 1.2 after the Enterprise signing engine upgrade.
First check LTV-SDO changes for Enterprise signing for common changes and whether you need to act.
The signer details stay the same, including the bankid-no signer attributes subject-dn, serialnumber, issuer-dn, date-of-birth, fnr and unique-id.
Do I need to act?
Yes. If you use the Enterprise Sign API (Sign API v1), this upgrade affects you. Read this page to find out whether you need to change your integration.
Certificates in the native signature
NativeSignatureQualifyingProperties/CertificateValues contains the signer's BankID certificate after the upgrade, replacing the BankID root CA certificate.
If you read a certificate from this element, update your code to expect the signer's certificate.
Audit trails
These events are no longer included after the upgrade:
- Creation audit trail:
invoked-oauth2Token,invoked-credentialsList,invoked-credentialsAuthorizeandinvoked-signaturesSignhash. - Signature verification audit trail:
prepare-validationandcompleted-validation. The signature verification audit trail is no longer included.
The creation audit trail contains started-transaction. If you read or display the removed events, update your code to work without them.
Text documents
For text/plain documents, signature labels change from PDF labels to labels reflecting the actual signature format.
<SignatureFormatFriendlyName>PAdES B-LT</SignatureFormatFriendlyName>
<NativeSdo Format="...:BankID-NO-SDO" MimeType="application/pdf" Version="1.0">...</NativeSdo>
<SignatureFormatFriendlyName>XAdES-BASELINE</SignatureFormatFriendlyName>
<NativeSdo MimeType="application/x-ltv-sdo" Version="1.0">...</NativeSdo>
Namespace declarations are omitted and ... marks shortened values.
If your code branches on SignatureFormatFriendlyName, NativeSdo/@Format or NativeSdo/@MimeType, accept the new labels and the absence of the Format attribute.
Checklist
- Check the common changes.
- Expect the signer's certificate if you read
CertificateValuesfrom the native signature. - Handle the removed BankID signing events and signature verification audit trail.
- Accept the new format labels if you sign text documents.