Service maintenance with customer test DNS update
Time: 2022-05-05 09:00 - 15:00 CEST
Update 6th May: Change has been rolled back and will be implemented on a later date, to be announced.
Nets will perform maintenance on the FTN/E-Ident, E-Signing and ID-Rights services in the customer test environment. The customer test platform will be upgraded through introduction of new servers. As a consequence of this upgrade the DNS will be updated to reflect new IP-addresses for our services when accessed from Internet. Details are described in the table below:
Services in production will not be affected, only the customer test services.
Service maintenance on database servers
Time: 2022-06-05 00:00-02:00 CEST
Nets will perform maintenance on the database servers used by the E-Ident service. During the service window there will be a short period of unavailability of about 5 to 10 minutes.
Required upgrade to use encrypted ID Token for FTN customers
Time: As soon as possible or the 15th September 2022 as the latest
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. This means that several customers need to update their implementation with support for encrypted ID Tokens and a few customers need to change the implementation from SAML to OIDC. Below are links to documentation regarding both encrypted ID Tokens, and the OIDC protocol.
Customers are kindly requested to update their implementation now and in any case well before the deadline 15th September 2022. Please
contact support to request update of your customer configuration and with other questions.
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):
-----BEGIN PUBLIC KEY-----
-----END PUBLIC KEY-----
Below is the same public key as above, but now formatted as a JWK (JSON Web Key):
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 3: Can we have a separate key for test and production?
Yes, we recommend that you create separate key-pairs for customer test and production.
Startup in test
Question 4: Could we enable encryption in test environment now?
Yes, you can start with customer test now, and later enable encryption in production.