Skip to content

remove nobankid reference to text signing #307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mickhansen merged 2 commits into from
Apr 1, 2026
+2 −31
Merged

remove nobankid reference to text signing #307

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
da45e4b
remove nobankid reference to text signing
mickhansen Mar 31, 2026
163f4f3
update NO BankID QES documentation
mickhansen Mar 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 2 additions & 9 deletions src/pages/signatures/guides/norwegian-bankid.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,20 +5,13 @@ sort: 20
title: Norwegian BankID QES
---

Stø, the company behind BankID requires that all merchants move to their new Signing API.
Stø, the company behind BankID requires that all merchants be moved to their new Signing API.
Copy link
Copy Markdown
Collaborator

@nmoskaleva nmoskaleva Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: should we say
"all merchants implement their new Signing API", instead of "be moved to"?
Since this is already a requirement.

Copy link
Copy Markdown
Collaborator Author

@mickhansen mickhansen Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nmoskaleva Idura does the implementation/moving

Copy link
Copy Markdown
Collaborator

@nmoskaleva nmoskaleva Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, then I agree 😊

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:
However, as signatures will be based on certificates rather than JWTs like other eIDs, there are some changes:

- A new `Signature` GraphQL subtype has been added, [`NorwegianBankIdSignature`](/signatures/graphql/schema/#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.

QES is enabled for all test signatures, and available on an opt-in basis for production signatures.

To opt in to production, adjust your [`criiptoVerify` evidence provider settings](/signatures/graphql/schema/#CriiptoVerifyProviderInput) settings so that:

- `loginHint` contains `nobankid_csc`
- `version` is `V2` or higher.

Please note: Norwegian BankID QES with [CSC](https://developer.bankid.no/bankid-esign-provider/apis/csc/CSC/) carries an increased eID cost per document.
22 changes: 0 additions & 22 deletions src/pages/verify/e-ids/norwegian-bankid.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,28 +192,6 @@ Idura _does not_ store the SSN itself, just the fact that the user has granted y

You can tweak core operational parameters and configure access to the optional user data on the [Norwegian BankID](https://dashboard.idura.app/providers/NO_BANKID) eID provider page of the Idura Dashboard.

## Signing text

Norwegian BankID supports signing text.

Text signing is triggered by using the `action` and `message` parameters [via login_hint](/verify/getting-started/oidc-intro/#the-loginhint-parameter).

- The `action` parameter must be set to `sign`
- The `message` parameter must be base64 encoded.

_Note: Signing produces very large JWTs that are not appropriate for authentication/Bearer header use_

Text signing has a different eID cost than authentication, please [contact Idura sales](https://www.idura.eu/contact) if you have questions.

<details>
<summary><strong>Example</strong></summary>

`login_hint=action:sign message:VmVuZG9yOgoKQ29vbCBEZWxpdmVyeQoKQW1vdW50OgoKMzAwIEVVUgoKCgpJIGFwcHJvdmUgdGhpcyB0cmFuc2FjdGlvbi4=`

Try out the example in [our URL builder](/verify/guides/authorize-url-builder/?acr_values=urn:grn:authn:no:bankid&action=sign&message=Vendor%3A%0A%0ACool%20Delivery%0A%0AAmount%3A%0A%0A300%20EUR%0A%0A%0A%0AI%20approve%20this%20transaction.)

</details>

## BankID Biometrics assurance level

BankID Biometrics assurance level is “Substantial”.
Expand Down
Loading