Security

The digital signature service uses two-way TLS to ensure the confidentiality and message integrity of the transport layer. The document package containing the documents to be signed is integrity-assured with ASiC-E.

Two-way TLS

To use the APIs, you need an organization certificate. Concerning purchase of and more information about the organization certificate, see purchase of an organization certificate. Here, you will also find information about which of the certificates you have that must be used for our service.

See also approved organization certificate in the public sector and certificate management in the public sector for more information about root and intermediate certificates.

Most HTTP clients have built-in support for two-way TLS. You can see examples of the implementation in the client library written in C# or the client library written in Java. The digital signature service only supports TLS 1.2 for two-way TLS.

You use your own certificate in keystore (for verification of your identity), og legger til the trust anchors (CA certificates) to the truststore (with which the server will verify its identity). Your certificate will be used for verification of your identity towards the server and the server will use Posten Norge AS’ certificate to verify its identity. Since the trust anchors are in the truststore you will obtain most of the validation from there (provided that your language/framework handles this). What you have to do manually is to validate that the certificate belongs to Posten Norge AS by checking the organization number stated in the Common Name.

A good tip is to use or take inspiration from Difi’s certificate validator.

Common problems when setting up two-way TLS

  • The wrong truststore is used for the client. In the test environment, the truststore must contain the test certificates, and in production there must be production certificates.
  • The certificate used is not an organization certificate. Organization certificates are typically issued by Buypass or Commfides.
  • The client does not support TLS v1.2. Java 6 does not support TLS v1.2; in Java 7 this must be added explicitly.
  • The certificate is issued by Commfide’s SHA-1 root certificate. Only certificates with SHA-256 from Commfides are supported. This primarily applies to older certificates.

Personal data

Personal data and sensitive personal data are only to be entered in the following fields in the XML in the requests towards the API:

  • personal-identification-number – signer’s national identity number or D number
  • title – the title/topic of the request, which summarizes what the signature request concerns
  • description – may contain a personal message, additional information or a description of the documents

Other fields may not contain sensitive personal data or personal data. For example, the reference (reference) will be used outside a secure context (e.g. in email notifications) and therefore may not contain personal data. See also the description of the API below.

For further details of the terms personal data and sensitive personal data see the website of the Norwegian Data Protection Authority.