Operational information

​​​​​​All coming customer affected changes for E-Ident.

​​​ ​

Service maintenance for Finnish bank S-Pankki

T​ime period: 2024-03-24 00:05 - 08:00 EET


The Finnish bank S-Pankki has announced a service window for their identification services. During the service window, identifications with S-Pankki through the FTN service will be unavailable.

​​ ​ Replacement of SSN in SUB for BankID Sweden

Time: 1st April 2024


When integrating E-Ident using OIDC protocol, the resulting ID Token contains a claim called "sub". After April 1, 2024, the value of the sub claim for BankID Sweden will no longer include social security number. An anonymous identifier will be used instead. The sub claim value will remain consistent for the same individual from this date onwards.

Customers using the sub claim to identify users should consider that the value will change after the given date. The "ssn" claim will still work as before.

FAQ: Encrypted ID Token for FTN customers


To be aligned with requirements to identity brokers from Traficom (Finnish Transport and Communications Agency), all FTN customers MUST use the OIDC protocol with encrypted ID Token in the communication with the FTN service. Below are links to documentation regarding both encrypted ID Tokens, and the OIDC protocol.


Frequently Asked Questions related to encrypted ID Token

Generate Public Key

Question 1: Is there any guide / example for us about how to generate and provide you with a public key?

Generation of an RSA public key should be done using your preferred encryption tool, and according to related documentation provided by said tool.

Here is an example on how you can generate a key-pair using the popular openssl command line tool:

openssl req -new -newkey rsa:2048 -keyout key.pem -pubkey -out pubreq.p10 -subj "/CN=MyKey"

The file key.pem will contain your password-protected private key that you must implement into your application. The file pubreq.p10 will contain both the public key and the CSR-request. The public key must be sent to us, and the CSR-request you can ignore.

Public Key Format

Question 2: In what format do you need encryption keys?

The public key must be provided for us in PEM format, as a JWK or as URL link to a JWKS on web.

Below is an example of a public key in PEM-format (base64-encoded ASN.1 binary):

-----END PUBLIC KEY-----

Below is the same public key as above, but now formatted as a JWK (JSON Web Key):

  "kty": "RSA",
  "n": "32frjzf3sUdKfHrwKWw56Kj1YXdQcQ-2BX4L5ZYFx1QztRcrQiz57yOtBBIsNCLmbLC0Gu-2dlKG4_FJVBcRIOgXD-LQW2IUnV0AFR2N8EVlbilQvkKSA0FAAb-0D-v8Y6xcjlu5QJOLtOEY09cAG3CseylRvNwnBJYwoainl7BEPAWjAAZ4FQV1PYrVFG7-YeyE33DH0FXG4VWOCvvCb537PZwbisTkXfDslJZg-v-KTyPCQUt7ZUwKJ3b-WoxdEhKOaI3Dt_A_N3oQhZrX-miH7MclhmOzNhayYCghyUks7CdPgy1fdRvhziFkwJ3chh3jhkJ4KEBnj0uVCrfSXw",
  "e": "AQAB"

A public key may also be added to a JWKS (JSON Web Key Set) on a publicly available web site. In this case, you must send us the URL, and we will register and use the URL to retrieve the public key. The advantage of publishing the key on your own web, is the fact that you may later update the key on your side, without involving us.

Key for test and prod

Question 3Can we have a separate key for test and production?

Yes, we recommend that you create separate key-pairs for customer test and production.