Signed Statement and native signature
Signed Statement and native signature with Norwegian BankID.
Development work for cross consumption runs from now until the end of January, and the cross consumption period will run throughout February.
1. What is changing
We are moving from the old BankID Server solution, NBID Server, to the new BankID Cloud Signature Consortium API. Because of this, the token inside the signature part of the ltvsdo will no longer be a SEID SDO, but instead a signed result following the eIDAS standard, respectively a PAdES created by the DSS library for PDFs and a XAdES built by the DSS library for text signing.
2. Who is affected
You are affected if you use Norwegian BankID signed statement or native signature through Signicat.
3. What this means for you
3.1 Data fields in the ltvsdo
Some data fields will no longer be available in the ltvsdo.
The ltvsdo will not include every field that existed in the old one.
For example, some information that was previously present in the ltvsdo will no longer be available in the new solution.
3.2 Data fields in the signature result inside the ltvsdo
Some data fields will no longer be available in the signature result inside the ltvsdo.
The new signature result inside the ltvsdo will not look and feel like the previous SEID SDO, and will not contain all information that could be retrieved from the SEID SDO.
For example, some information that was previously part of the SEID SDO will not be present in the new signature result.
3.3 You may need to update your system
If your system depends on fields that are not provided in the new solution, you will need to update it to use the newer fields.
4. Timeline and development work
- Development work for cross consumption, from now until the end of January
- Cross consumption period, throughout February
You should plan and complete any necessary updates within this timeframe so that your signed statement and native signature flows continue to work with the new BankID Cloud Signature Consortium API.