Idura changelog

Approve a text with Norwegian BankID

Thu, 05 Nov 2026 00:00:00 GMT

Approve a text with Norwegian BankID

Your users can now approve a text with Norwegian BankID, such as an agreement or a change to their account, and log in at the same time. BankID shows the text before the user authenticates, and the ID token holds the approved text and its digest from BankID. Add the evidence scope to also get signed evidence of the approval from BankID, which a third party can verify.

You ask for an approval with authorization_details in a pushed authorization request from your backend.

For more details, see approve a text with Norwegian BankID.

Security Advisory: Signatures python SDK

Mon, 26 Oct 2026 00:00:00 GMT

Security Advisory: Signatures python SDK

The Signatures Python SDK has a transitive dependency on certifi. certifi versions before 2026.10.19 trust the emSign ECC Root CA - G3 root certificate, and the compromised intermediate eMudhra CAs that chain to it (GHSA-6q48-6c7w-9gw2 (https://github.com/advisories/GHSA-6q48-6c7w-9gw2)).

The SDK uses the certifi bundle to verify TLS connections to the Signatures API. An on-path attacker holding one of the compromised keys could intercept or modify that traffic.

Neither the SDK nor its dependencies place an upper bound on certifi, so no new SDK version is needed. Upgrade certifi to 2026.10.19 or later in your environment or lockfile.

Deprecating Signatures endpoint

Mon, 14 Sep 2026 00:00:00 GMT

Deprecating Signatures endpoint

We are deprecating the https://signatures-api.criipto.com/v1/graphql URL in favor of https://signatures.idura.app/v1/graphql.

We recommend switching for improved performance and to ensure uninterrupted usage. The https://signatures-api.criipto.com/v1/graphql URL will be taken down on October 4, 2027.

Improved order flow for Swedish BankID

Thu, 16 Jul 2026 00:00:00 GMT

Improved order flow for Swedish BankID

The process for ordering Swedish BankID has been simplified and streamlined, such that we can process your orders faster. In practice, this should result in more orders being approved first try, allowing you to go live faster.

Instead of manually filling out a PDF form and emailing it to us, orders are now submitted directly from the Idura dashboard. The dashboard order form guides you through the required information and shows the status of your order as it is being processed.

For more details, see order Swedish BankID.

Improved order flow for Norwegian BankID

Tue, 14 Jul 2026 00:00:00 GMT

Improved order flow for Norwegian BankID

The process for ordering Norwegian BankID has been simplified and streamlined, such that we can process your orders faster. In practice, this should result in more orders being approved first try, allowing you to go live faster.

Instead of manually filling out the predefined template over email, orders are now submitted directly from the Idura dashboard. The dashboard order form guides you through the required information and shows the status of your order as it is being processed.

This, together with a new revised internal process, means you have to provide less information than before. Most importantly, you don’t need a Norwegian bank account to apply anymore.

For more details, see order Norwegian BankID.

Retrieving form field values from PDF documents

Tue, 19 May 2026 00:00:00 GMT

Retrieve form field values from PDF documents in Signatures

It was previously not possible to retrieve the values of the form fields after a signatory had filled and signed the document without looking at the document.

It is now possible to programmatically retrieve the entered form field values either via our GraphQL endpoint or as a file attachment in the document.

See PDF form filling guide for more information.

Support cooldown period and Finnish language

Tue, 19 May 2026 00:00:00 GMT

Support cooldown period in Signatures

We now support defining a cooldown period before a signatory is allowed to sign in case of any business requirements.

See Cooldown guide for more information.

Signatures puhuu nyt myös suomea!

Signatures now speaks Finnish as well!

Deprecation notice for Signing via WS-Federation

Sat, 09 May 2026 00:00:00 GMT

Deprecation notice: Signing via WS-Federation

Idura Verify has supported text signing via the WS-Federation protocol since 2016.

When text signing via WS-Federation was launched, many of the available e-IDs supported text signing.

Today, only Swedish BankID supports text signing, which is already available via a more secure OpenID Connect based implementation.

From May 11th, text signing via WS-Federation will start failing in the test environment, to warn customers of the upcoming deprecation.

End of life

Signing via the WS-Federation protocol will be removed entirely from the Idura Verify product on 2027-05-09.

New Analytics Page in our Dashboard

Wed, 29 Apr 2026 00:00:00 GMT

New Analytics Page in our Dashboard

After eight months of renovation and a deep dive into user feedback, we are excited to reveal our fully redesigned Analytics Page.

What’s New?

The new page introduces focused Usage Data views. You can now filter and analyze your volume across three primary dimensions:

By Product: Get a clear breakdown across our expanded product suite, including Idura Verify, Idura Signatures, and Age Verification.
By Domain/Application: If you run multiple applications, you can now see exactly which one is driving your traffic and costs.
By eID: Discover which electronic identities (e.g., MitID, BankID, Freja eID) your users actually use, so you can better understand their preferences.

Why the Change?

Our original analytics suite was built in an Idura Verify-only world and was due for a major makeover. We’ve since introduced new products and features that we couldn’t properly represent in the old framework.

We worked hard to build a more robust experience from the ground up, rooted in customer interviews and feedback. The biggest request from developers and product owners was for better visibility into where and when their eID authentications were being spent. The updated page reflects those wishes and aligns the UI design with our new brand identity.

How to Access It?

Found a bug or have feedback for our dashboard? Reach out to us at support@idura.eu.

Support preserving original structure for PDF

Fri, 10 Apr 2026 00:00:00 GMT

Preserve Original Structure for PDFs in Signatures

Previously, we attempted to recreate documents to fix errors before signing and avoid breaking signatures, or when features like document ID watermarking or a custom seal page template were required.

However, in some scenarios, the original document structure must be preserved. For example, if the signing process isn’t allowed to change the document, or if the document has already been certified by a third party, recreating it would invalidate the certification.

See more at Signatures examples

Upcoming change of default View version

Tue, 17 Mar 2026 00:00:00 GMT

This is a notice that, from 2026-04-17, we will always render the latest view version (currently 2025-01-01), for all customers without any custom CSS, or custom UI.

You can check if this change affects you by going to https://dashboard.idura.app/styling.

If the View version field shows 2025-04-01, you are already on the most recent version, and you will not be affected by this change.
If the View version field shows Unified:
- If you are not using custom CSS, or custom styling, you will be switched to the new version.
- If you are using custom CSS, or custom styling, nothing will happen. However, we still urge you to test the new version in your own time, and switch to it as soon as possible.

What happens when the view version is changed?

In July 2025, Swedish BankID introduced stronger accesibility requirements around QR codes ( see the original changelog entry). This lead us to change the HTML and CSS we use to render the QR code, which again might break any custom styling of the QR code on your side.

Upgrading to the 2025-04-01 view version also brings multiple new features (such as new eID logos) and bug fixes.

Support PDF signature seal scaling in Signatures

Fri, 06 Mar 2026 00:00:00 GMT

Support PDF signature seal scaling in Signatures

Up until now the PDF signature seals were using default dimensions, however, to support cases where the seal might be too big, it is now possible to define a scale. The scale supports the range 0.2 to 1.0, both included, in increments of 0.1. In case of other values that fall in that range, the scale value will be rounded down, e.g., 0.2345 => 0.2.

See PDF signature seal scaling example.

Logo on eID selector page (Signatures)

Wed, 28 Jan 2026 00:00:00 GMT

Logo on eID selector page in Signatures

Previously, the logo was only seen on the documents overview page that was only present when the signature order contained more than one document. However, now the logo is both shown on the documents overview page as well as the eID selector page.

Removal of PDF bookmarks

Mon, 19 Jan 2026 00:00:00 GMT

Removal of PDF bookmarks

When combining multiple PDF documents in Adobe, a default enabled option creates bookmarks for each of the combined PDFs. Attempting to sign such a combined document likely renders the signatures invalid as Adobe believes the document to have been altered.

We have extended the PadesDocumentInput, when creating a signature order, with a property removeBookmarks. Bookmarks will be removed from the signed document(s) where the flag is set.

To better support flexible flows, e.g., let the end user decide, the validateDocument mutation returns whether the provided document contains any bookmarks.

Drawback is that users that previously relied on the bookmarks for navigation will no longer have the option, however, signatures are now correctly shown as valid.

Please note: bookmarks generated from headings in Word or Google Docs don’t suffer the same issue, it’s only after such PDFs have been combined the issue occurs.

EUTL Signatures

Thu, 18 Dec 2025 00:00:00 GMT

EUTL for Signatures

The Idura Signatures product will move from AATL to EUTL certificates and timestamping on January 8th, 2026.

This has no negative effects*, but has the positive effect that signed documents can now be validated in both Adobe and the EU DSS validator.

* Users with very old versions of Adobe Reader will have to update their EUTL trust list in the Adobe Reader Trust Manager.

Signatory Roles

Tue, 09 Dec 2025 00:00:00 GMT

Signatory Roles

Signatory roles are used to designate what actions a given signatory is allowed to perform. A signatory’s role can be set when adding a signatory to a signature order.

Signatory roles aim to cover complex signing scenarios, such as, requiring specific people approve before a signature order can be closed/signed or allowing certain people access to the signature order thoughout its lifetime.

Please read the more in-depth guide under Signatures > Guides > Signatory Roles

Norwegian BankID QES

Tue, 25 Nov 2025 00:00:00 GMT

Norwegian BankID QES

Stø, the company behind BankID requires that all merchants move to their new Signing API. This is beneficial, in that future signatures with BankID will be at the highest European level, QES.

However, as signatures will then no longer be based on JWTs, it has a few breaking changes:

A new Signature GraphQL subtype has been added, NorwegianBankIdSignature of which you can request claims.
Evidence Validation must be done on either ssn or uniqueuserid to work.
ssn scope must specifically be added to evidence provider settings if nnin is required.

Please note: Norwegian BankID QES with CSC carries an increased eID cost per document.

Viewer role added for signing

Tue, 04 Nov 2025 00:00:00 GMT

Viewer role

You can now specify a signatoryRole when adding signatories.

In addition to the default SIGNER role, a new VIEWER role lets you add participants who can view the documents without signing. Viewers do not block signing in parallel flows and can download the signed document once the signature order has been closed.

Sequential signing is now possible

Wed, 08 Oct 2025 00:00:00 GMT

Signing sequence

You can now control signing order in your signature workflows by setting a signingSequence on signatories. Signatories with lower numbers sign first, while those with the same number can sign in parallel.

An example can be found in the Signatures documentation.

Introducing custom seals page template feature

Fri, 15 Aug 2025 00:00:00 GMT

Custom seals page template

We added custom seals page template to the Signatures API. The new add-on feature gives you full control over the signature seals page. Instead of the default blank page, you can now provide your own branded PDF template, making it easy to add your company’s logo and colors to the signed document.

Walk through an interactive tour to see it in action.

Introducing FrejaID

Fri, 25 Apr 2025 00:00:00 GMT

Swedish FrejaID

Authentication via Idura Verify now supports Swedish FrejaID. With FrejaID, you can authenticate users in Sweden even if they do not have a Swedish personal identity number. This unlocks government-approved electronic ID for historically under-served segments of the population such as recent immigrants.

If you are interested in testing it out for yourself, read our documentation on FrejaID to get started.

Introducing changeSignatureOrder mutation

Thu, 03 Apr 2025 00:00:00 GMT

New `changeSignatureOrder` mutation

We have introduced a new mutation that enables changing a signature order after creation. Initially it supports changing maxSignatories until the first signatory has signed. Please reach out if you have other needs for modifying signature orders post creation.

An example can be found in the Signatures documentation.

The mutation is supported in .NET and Node.JS SDK v1.21.0.

Stronger accessibility requirements for Swedish BankID

Wed, 02 Apr 2025 00:00:00 GMT

From July 2025, stronger requirements regarding accessibility must be fulfilled to meet legal demands. Amongst other things, these will affect the two-device flow for BankID where the animated QR code is used.

Learn more about the new requirements

In order to comply with the new QR code UI requirements, Idura must make adjustments to our UI (HTML & CSS), so that users may click the QR code to view it in fullscreen.

This can cause breaking changes to customers who have custom CSS, so customers must explicitly enable the UI update. To comply with the new requirements, you must enable the UI update before July 2025.

You can opt-in to the UI update for the test environment, and even per application, before doing so in production.

To opt-in at a tenant environment level:

Open dashboard
Navigate to Styling screen
Select 2025-04-01 in the “View version” dropdown
Click save

To opt-in at an application level:

Open dashboard
Navigate to Applications screen
Select the application you wish to upgrade
Click the “UI” tab
Disable “Use default” for the “View version” option
Select “2025-01-04” in the “View version” dropdown
Click save

Introducing Personalausweis and batch signatories

Thu, 20 Feb 2025 00:00:00 GMT

German Personalausweis

Authentication via Idura Verify now supports the German national identity card Personalausweis. This means that you can now electronically authenticate users in Germany quickly and easily.

You can read more about the Personalausweis on the German government Personalausweis portal. If you are interested in testing it out for yourself, read our documentation on Personalausweis to get started.

Batch signatories for signatures

As a step towards enabling interacting with large batches of signature orders, we have introduced a feature for batching signatories across one of more signature orders. A batch signatory can then be used to invoke a single action and have it performed automatically across every signatory.

As batch signatories can be used to sign multiple, different signature orders at once, some requirements exist. A more detailed explanation, and interactive tour, can be found at the batch signatory guide page.

Signatory UI settings and webhook signing

Sat, 25 Jan 2025 00:00:00 GMT

Signatory UI settings

Historically signature UI settings for users have been configured globally on the signature order.

This had some drawbacks, as users might reside in different countries and prefer different languages.

It is now possible to also define UI settings on a per signatory basis, See example

Webhook signing

Until now, there was no way to validate the authenticity of a signature webhook at the time of the request.

We relied on the fact that webhooks contained no actual data, but only identifiers, allowing clients to query our API based on the data in the webhook. This ensured that only authenticated clients could access signature data.

However, it was brought to our attention that an attacker could use the webhook to increase the number of requests a well-behaving client would have to make to our API, potentially triggering rate limits.

To address this, we introduced the option to configure a webhook secret, which adds an HMAC-SHA256 signature to each signature webhook invocation.

You can read more about configuring and validating webhook secrets and also try it out in our webhook tester.

MitID Controlled Transfer

Fri, 04 Oct 2024 00:00:00 GMT

Authentication via Idura Verify now supports starting a session for MitID Controlled Transfer.

MitID Controlled Transfer lets you perform cross-broker SSO, that is, transfering an authenticated MitID user from one service provider to another, without requiring the other service provider to reauthenticate the user.

This is useful for cases where shared data services may require a valid MitID authentication to serve data for the user, but you do not wish to trigger authentication twice for the user.

Read the guide on how to implement Controlled Transfer

Idura changelog

Approve a text with Norwegian BankID

Approve a text with Norwegian BankID

Security Advisory: Signatures python SDK

Security Advisory: Signatures python SDK

Deprecating Signatures endpoint

Deprecating Signatures endpoint

Improved order flow for Swedish BankID

Improved order flow for Swedish BankID

Improved order flow for Norwegian BankID

Improved order flow for Norwegian BankID

Retrieving form field values from PDF documents

Retrieve form field values from PDF documents in Signatures

Support cooldown period and Finnish language

Support cooldown period in Signatures

Signatures puhuu nyt myös suomea!

Deprecation notice for Signing via WS-Federation

Deprecation notice: Signing via WS-Federation

End of life

New Analytics Page in our Dashboard

New Analytics Page in our Dashboard

What’s New?

Why the Change?

How to Access It?

Support preserving original structure for PDF

Preserve Original Structure for PDFs in Signatures

Upcoming change of default View version

What happens when the view version is changed?

Support PDF signature seal scaling in Signatures

Support PDF signature seal scaling in Signatures

Logo on eID selector page (Signatures)

Logo on eID selector page in Signatures

Removal of PDF bookmarks

Removal of PDF bookmarks

EUTL Signatures

EUTL for Signatures

Signatory Roles

Signatory Roles

Norwegian BankID QES

Norwegian BankID QES

Viewer role added for signing

Viewer role

Sequential signing is now possible

Signing sequence

Introducing custom seals page template feature

Custom seals page template

Introducing FrejaID

Swedish FrejaID

Introducing changeSignatureOrder mutation

New changeSignatureOrder mutation

Stronger accessibility requirements for Swedish BankID

Introducing Personalausweis and batch signatories

German Personalausweis

Batch signatories for signatures

Signatory UI settings and webhook signing

Signatory UI settings

Webhook signing

MitID Controlled Transfer

New `changeSignatureOrder` mutation