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 authentication-based signing

When Signicat upgrades the engine behind your Enterprise Sign API (Sign API v1) integration, you keep using the same API. The LTV-SDO returned for authentication-based signing changes as described below.

Authentication-based signing with any eID is affected. In the REST API, its method type is AUTHENTICATION_BASED (signatureMethods[].type). The changes shared by Signed Statement methods are also covered below. For Swedish BankID, also review the Signed Statement changes.

Check the upgrade schedule and handling of existing sessions before testing your integration.

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.

If you only archive the LTV-SDO, you need no changes.

If you only read signer details, you need no changes unless your integration expects SignerNationality to be absent when includeNationalIdInLtvSdo is false. The new engine writes the country associated with the eID to this field for every eID. If you rely on its absence, update your integration to accept the value. See the comparison in Other changes.

If you validate the seal or embedded SAML signature, check the SAML issuer, or read signature context components or audit events, update your integration for the changes below.

The signed document, its digest and the configured LTV-SDO version stay the same. Supported versions are 2.3, 2.4 and 2.5. The new engine does not write versions 2.0 to 2.2 or package existing LTV-SDOs of those versions as PAdES.

LTV-SDO seal​

The seal changes from RSA (rsa-sha256) to ECDSA (ecdsa-sha256) and uses a new certificate. Both certificates are issued to SIGNICAT AS. If you validate the seal with your own code, support ECDSA. If you pin the seal certificate, add the new certificate and keep trusting the current one for existing LTV-SDOs.

Before your upgrade, follow the LTV-SDO seal certificate guidance to request the new certificate and trust chain.

The seal structure also changes. Support both forms in your validator.

Embedded SAML response​

Authentication/SAMLResponse contains the SAML 1.1 response from the signer's authentication. Its format and attributes with a value stay the same; empty attributes are omitted. This applies to every SAML attribute, including <ns>:document.description. If your integration requires an attribute that can be empty, update it to handle the attribute's absence.

The response signature uses the LTV-SDO seal certificate instead of the identity portal's certificate, and the algorithm changes from rsa-sha256 or rsa-sha1 to ecdsa-sha256.

The new assertion issuer (saml:Assertion@Issuer) is api.signicat.com/sign. Read the current issuer from an LTV-SDO produced by your integration before the upgrade. If you check the issuer or validate the signature, accept the new issuer, trust the seal certificate for SAML responses and support ECDSA before your upgrade. Keep trusting the current issuer and certificate for existing LTV-SDOs.

The new engine omits samlp:Response@Recipient. If you read this attribute, handle its absence.

Signature context and friendly names​

SignatureCreationContext and SignatureVerificationContext use the components signature-creation and sign-ui instead of ltvsdo, Signicat Services Sign Portal and signflow. The context Type="signicat", the user-agent component and the attribute values stay the same.

Read attributes by name rather than position, and avoid depending on component names or versions.

SignatureTypeFriendlyName remains Signicat Sign (<friendly name>), or Signicat Sign without a friendly name. Some eIDs get a different suffix because the new engine has different fallback names. For Signed Statement, the value is always Signicat Sign. Read the eID from the SAML response instead of matching this friendly name exactly.

Audit trail​

The events started-signature-session, presented-document-to-signer, signer-consented-to-document-content and verified-saml-response remain. The new engine never writes signer-chose-to-proceed.

The new engine also does not write signer-consented-to-additional-content or signer-chose-handwritten-only. Other audit differences are listed in Other changes.

Handle missing events and read entries by name rather than position. Parse timestamps as ISO 8601 with any UTC offset and optional fractional seconds.

Signed Statement​

The new engine includes SignedStatement only for eIDs whose signature it can embed. Other eIDs use authentication-based signing without SignedStatement. If you read this element, handle its absence. Confirm support for each eID you use before the upgrade.

For several documents, you still receive one LTV-SDO per document with the same statement and signature. NonVisibleSignText and DocumentIndex depend on whether the eID supports a non-visible signature part.

If your order supplies sign text, VisibleSignText keeps that text. The default text differs as described below.

Handwritten signatures and Signed Statement methods​

Customers whose orders combine a handwritten signature with an eID, or a BankID Signed Statement with other methods in one task, are upgraded once the new engine supports them.

After your upgrade, every new order goes to the new engine. If it does not support an order, it returns an error rather than sending the order to the current engine.

Handwritten signatures with an eID​

The new engine does not yet support orders combining a handwritten signature with an eID, through either SOAP or REST. Support is planned.

Signed Statement methods​

The new engine supports Signed Statement for Swedish and Norwegian BankID. If all methods in a task are signed statements from the same BankID, it creates one BankID signature over the statement.

The new engine refuses a task that combines a BankID Signed Statement with other methods or with the other BankID.

Signed Statement methods for other eIDs use authentication-based signing. Freja and Buypass Signed Statement are not offered.

Other handwritten signature changes​

Images of the signer's ID paper (HandwrittenSignatureQualifyingProperties/IdPaper) are not supported on the new engine.

We will share more information about orders with a handwritten signature and no eID soon.

Other changes​

Prepare your integration to handle both forms.

Set sign text in your order if you need control over the consent or statement wording and language. Read attributes by name. If you use DETACHED packaging, handle the original document being included in the LTV-SDO.

Checklist​

  • Support ECDSA and trust both seal certificates.
  • Support both seal structures.
  • Trust the seal certificate for embedded SAML signatures and accept the new issuer.
  • Handle a missing SAML Recipient attribute.
  • Read attributes and audit entries by name, and handle missing events.
  • Parse timestamps as ISO 8601 with optional fractional seconds.
  • Avoid depending on component names or exact friendly names.
  • Confirm Signed Statement support for each eID and handle a missing SignedStatement.
  • Set sign text in the order if you need specific wording or language.
  • Test your integration in pre-production before the production upgrade.