LTV-SDO changes for Swedish BankID third-party signing
Our Swedish BankID third-party (PKI) signing method uses the signer's certificate to create the signature for PDF and text documents. Its method type is THIRD_PARTY (signatureMethods[].type in the REST API). The method name can be anything, but a common name is sbid-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-se:firstname and bankid-se:lastname signer attributes.
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.
Data signed by BankID
The BankID signature in NativeSdo contains usrNonVisibleData: base64-encoded data that BankID signs together with the text the signer sees. It describes the signed documents. After decoding it, expect the new JSON structure.
{
"attachments": [
{
"digestValue": "...",
"digestMethod": "...",
"secondaryDigestValue": "...",
"secondaryDigestMethod": "...",
"documentDescription": "Loan agreement",
"mimeType": "application/pdf",
"serialNumber": "..."
}
]
}
{
"documentsToSignHash": "...",
"documentsToSign": [
{
"documentToSignId": "...",
"type": "...",
"contentUrl": "...",
"hash": "fcf3c1a4...dc1d48",
"hashAlgorithm": "..."
}
]
}
The examples are simplified; ... marks shortened values.
If you decode usrNonVisibleData, update your parser to handle documentsToSign instead of attachments. To check a document against the signature, compare hash with the document's SHA-256 digest in hexadecimal.
Text documents
For text/plain documents, usrNonVisibleData is omitted before the move. After the move, it is always included with the structure above. The visible text (usrVisibleData) remains the document's own text.
Update code that expects usrNonVisibleData to be empty for text documents.
Creation audit trail
After the upgrade, the creation audit trail omits these events:
user-selected-bankid-deviceinvoked-sign-callsecurity-app-started
The collected-signature-and-validation-data event no longer contains request-order-ref, the BankID order reference.
The audit trail still contains started-transaction, verified-signature and collected-signature-and-validation-data. If you read or display audit events, handle the removed events and the absence of the BankID order reference.
Checklist
- Check the common changes.
- Update your
usrNonVisibleDataparser for the new JSON structure, including for text documents. - Handle the removed audit events and BankID order reference.