For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

For the complete documentation index, see llms.txt

LTV-SDO changes for Swedish BankID Signed Statement

With our Swedish BankID Signed Statement feature, the signer approves one or more documents in a single BankID signature. You receive one LTV-SDO per document. Its method type is SIGNED_STATEMENT (signatureMethods[].type in the REST API). The method name can be anything, but a common name is sbid-sign. The LTV-SDO version remains 2.x 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 and DocumentIndex stay the same. SAML response attributes with a value stay the same; empty attributes are omitted. If your integration requires an attribute that can be empty, update it to handle the attribute's absence. If your order supplies sign text, VisibleSignText keeps that text. For changes to default text, friendly names and audit events, review the shared Signed Statement changes.

SAML response signature​

The SAML response inside Authentication uses the LTV-SDO seal key and certificate after the upgrade, replacing the current engine's Signicat External CA (2048) certificate. The new key is an elliptic curve (EC) key, and the signature algorithm changes from rsa-sha256 to ecdsa-sha256.

The new SAML issuer is api.signicat.com/sign.

Read the current issuer from an LTV-SDO produced by your integration before the upgrade.

If you validate the SAML signature or check its issuer, add the new issuer and certificate to your trust configuration before your upgrade. Follow the LTV-SDO seal certificate guidance to request the certificate and trust chain. Make sure your library supports ECDSA, and keep trusting the current issuer and certificate for existing LTV-SDOs.

NonVisibleSignText​

SignedStatement/NonVisibleSignText lists the documents the signer approved, exactly as BankID signed them. Its JSON structure changes from attachments to documentsToSign.

NonVisibleSignText before the upgrade
{
"attachments": [
{
"index": 0,
"documentDescription": "Loan agreement",
"mimeType": "application/pdf",
"primaryDigestValue": "...",
"primaryDigestMethod": "...",
"secondaryDigestValue": "...",
"secondaryDigestMethod": "..."
}
]
}
NonVisibleSignText after the upgrade
{
"documentsToSignHash": "...",
"documentsToSign": [
{
"documentToSignId": "...",
"type": "...",
"contentUrl": "...",
"hash": "fcf3c1a4...dc1d48",
"hashAlgorithm": "..."
}
]
}

The examples are simplified; ... marks shortened values.

DocumentIndex still gives the document's position in the list.

If you parse NonVisibleSignText, update your parser for the new structure. A parser that requires attachments fails after the upgrade. To check a document, compare hash with the document's SHA-256 digest in hexadecimal.

Checklist​

  • Check the common changes.
  • Accept the new SAML issuer and certificate, and support ECDSA in your validator.
  • Update your NonVisibleSignText parser for the new JSON structure.
On this page