All Systems Operational
E-Ident
Operational
E-Ident
Operational
ID Verifier
Operational
E-Signing
Operational
E-Signing
Operational
Archive
Operational
DocArc
Operational
E-Archive
Operational
Meldingsarkiver
Operational
e-Nett
?
Operational
IDP’s 3rd Party Dependencies
Operational
MitID
Operational
FTN Aktia
Operational
FTN Danske Bank
Operational
FTN Nordea
Operational
FTN Oma SP
Operational
FTN OP
?
Operational
FTN Pop Pankki
Operational
FTN S-Pankki
Operational
FTN Telia
Operational
Swedish BankID
Operational
Norwegian BankID
Operational
Smart-ID
?
Operational
Mobile-ID
?
Operational
Buypass
?
Operational
ID-Rights
Operational
ID-Rights
Operational
Experian
?
Operational
Virre
Operational
TrustPortal
Operational
e-Consent
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
3rd party maintenance on FTN Finland Sep 21, 2025 04:00-13:30 CEST
THIS NOTIFICATION APPLIES TO:
Customers using FTN Finland
DESCRIPTION:
FTN Finland is announcing a maintenance window. Telia identification and signing will not be available
CONSEQUENCE:
During the service window, FTN Finland services will be unavailable.
Affected banks:
- Aktia Bank
- Bonum Bank
- Handelsbanken (Finland)
- Oma Savings Bank
- POP Banks
- Savings Banks
- Central Bank of Savings Banks Finland
NOTE: Questions can be directed to support.esecurity@nets.eu
Posted on Sep 16, 2025 - 16:33 CEST
Customers using FTN Finland
DESCRIPTION:
FTN Finland is announcing a maintenance window. Telia identification and signing will not be available
CONSEQUENCE:
During the service window, FTN Finland services will be unavailable.
Affected banks:
- Aktia Bank
- Bonum Bank
- Handelsbanken (Finland)
- Oma Savings Bank
- POP Banks
- Savings Banks
- Central Bank of Savings Banks Finland
NOTE: Questions can be directed to support.esecurity@nets.eu
Posted on Sep 16, 2025 - 16:33 CEST
E-Archive maintenance on 22nd of September Sep 22, 2025 22:00-23:00 CEST
THIS NOTIFICATION APPLIES TO:
Customers using Archive - E-Archive
DESCRIPTION:
Archive service (E-Archive) will have a urgent maintenance on 22nd of September. This will affect the mentioned service.
CONSEQUENCE:
During the service window, Archive services shall be unavailable for 1 minute. Time of unavailability is during the scheduled maintenance window.
NOTE: Questions can be directed to support.esecurity@nets.eu
Posted on Sep 18, 2025 - 08:59 CEST
Customers using Archive - E-Archive
DESCRIPTION:
Archive service (E-Archive) will have a urgent maintenance on 22nd of September. This will affect the mentioned service.
CONSEQUENCE:
During the service window, Archive services shall be unavailable for 1 minute. Time of unavailability is during the scheduled maintenance window.
NOTE: Questions can be directed to support.esecurity@nets.eu
Posted on Sep 18, 2025 - 08:59 CEST
3rd party planned maintenance on Telia ID broker, Telia Mobile ID, and Telia Sign Services Sep 22, 2025 23:05 - Sep 23, 2025 01:05 CEST
Telia Identification Service will be performing maintenance work regarding Telia ID broker, Telia Mobile ID, and Telia Sign Services.
There may be small disruptions to the services during the maintenance work.
Posted on Sep 09, 2025 - 14:18 CEST
There may be small disruptions to the services during the maintenance work.
Posted on Sep 09, 2025 - 14:18 CEST
Sunset of Norwegian BankID Server Oct 1, 2025 10:00-12:00 CEST
THIS NOTIFICATION APPLIES TO:
Customers of Signing & Identification services using Norwegian BankID
TIMELINE FOR CHANGE:
From: Q4’ 2025
DESCRIPTION:
The Norwegian BankID is sunsetting BankID Server for Java & C. As a result, all customers using Norwegian BankID Server API must migrate to the new Norwegian BankID OIDC before Q4’ 2025.
To comply with this, you have two integration options:
- Direct Integration with BankID – similar to your current setup.
- Integration via IN Groupe’s E-Ident Service.
Next steps,
1. Sign an Agreement with IN Groupe
- If you are already using Norwegian BankID Biometrics, no agreement is needed.
- IN Groupe’s Sales team will contact you for agreement signing and to provide legal/financial details.
2. Order a New Norwegian BankID Merchant Certificate
- This must be obtained from Norwegian BankID and shared with IN Groupe.
Affected customers will be contacted by either IN Groupe’s Sales team or Customer Success team.
NOTE:
Questions can be directed to support.esecurity@nets.eu
Posted on Apr 04, 2025 - 10:28 CEST
Customers of Signing & Identification services using Norwegian BankID
TIMELINE FOR CHANGE:
From: Q4’ 2025
DESCRIPTION:
The Norwegian BankID is sunsetting BankID Server for Java & C. As a result, all customers using Norwegian BankID Server API must migrate to the new Norwegian BankID OIDC before Q4’ 2025.
To comply with this, you have two integration options:
- Direct Integration with BankID – similar to your current setup.
- Integration via IN Groupe’s E-Ident Service.
Next steps,
1. Sign an Agreement with IN Groupe
- If you are already using Norwegian BankID Biometrics, no agreement is needed.
- IN Groupe’s Sales team will contact you for agreement signing and to provide legal/financial details.
2. Order a New Norwegian BankID Merchant Certificate
- This must be obtained from Norwegian BankID and shared with IN Groupe.
Affected customers will be contacted by either IN Groupe’s Sales team or Customer Success team.
NOTE:
Questions can be directed to support.esecurity@nets.eu
Posted on Apr 04, 2025 - 10:28 CEST
Production Update: Removal of BankID on Mobile Support Scheduled for October 8, 2025 Oct 8, 2025 10:00-12:00 CEST
The BankID on Mobile service was discontinued as of September 1, 2024. As a result, we are planning to remove all merchant configurations related to Bank ID on Mobile (bidMob) from the database. This includes deprecating support for the following parameters:
• amr_values=no_bidmob
• forcepkivendor=no_bidmob
CONSEQUENCE:
This update has already been deployed to our Pre-production environment and is available for testing and verification. We intend to implement the same change in the Production environment on October 8, 2025.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Posted on Sep 08, 2025 - 10:54 CEST
• amr_values=no_bidmob
• forcepkivendor=no_bidmob
CONSEQUENCE:
This update has already been deployed to our Pre-production environment and is available for testing and verification. We intend to implement the same change in the Production environment on October 8, 2025.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Posted on Sep 08, 2025 - 10:54 CEST
Upcoming changes for Norwegian BankID on the OpenID Connect platform on 28th of October 2025. Oct 28, 2025 11:00-13:00 CET
DESCRIPTION:
Norwegian BankID has announced following updates to the OpenID Connect platform, effective from 28th October’ 2025:
• Additional security requirements for all clients
• API Version 4 is standard for all Clients
• By the end of the year, we are also removing the experimental Consent service that provides additional userdata.
CONSEQUENCE:
• Deprecation of BankID Server related claims and BankID Proof: The 'verification_info' attribute, which contains the BankID Proof in the E-Ident userinfo endpoint response, will no longer be available and will therefore be removed.
• By the end of 2025, the Consent page for collecting email, address, and phone number during BankID authentication via the BankID NO server will be removed. Additionally, E-Ident will no longer return email, address, or phone number in the ID token or via the userinfo endpoint.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Posted on Jun 30, 2025 - 17:30 CEST
Norwegian BankID has announced following updates to the OpenID Connect platform, effective from 28th October’ 2025:
• Additional security requirements for all clients
• API Version 4 is standard for all Clients
• By the end of the year, we are also removing the experimental Consent service that provides additional userdata.
CONSEQUENCE:
• Deprecation of BankID Server related claims and BankID Proof: The 'verification_info' attribute, which contains the BankID Proof in the E-Ident userinfo endpoint response, will no longer be available and will therefore be removed.
• By the end of 2025, the Consent page for collecting email, address, and phone number during BankID authentication via the BankID NO server will be removed. Additionally, E-Ident will no longer return email, address, or phone number in the ID token or via the userinfo endpoint.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Posted on Jun 30, 2025 - 17:30 CEST
Upcoming changes for Norwegian BankID technical implementation Oct 28, 2025 12:31-13:31 CET
Norwegian BankID has announced upcoming changes to its technical implementation. Please refer https://developer.bankid.no/bankid-oidc-provider/important-updates-04-2025/
If you have any questions or require further assistance, please contact our customer success team at: https://ingroupe.com/in-trust-services-support-contact-page/
Best Regards,
IN Groupe
Posted on May 19, 2025 - 12:35 CEST
If you have any questions or require further assistance, please contact our customer success team at: https://ingroupe.com/in-trust-services-support-contact-page/
Best Regards,
IN Groupe
Posted on May 19, 2025 - 12:35 CEST
Customer action needed: Update on Traficom requirement for customers on Finnish Trust Network (FTN) Dec 31, 2025 10:00-12:00 CET
This is to inform you that we have received an update to Traficom regulation with a new requirement affecting all customers on (Finnish Trust Network) FTN. The new requirement makes the use of signed authentication requests mandatory. The signed authentication requests is also called Signed Request Object in the OIDC specification.
Consequence for IN Groupe:
IN Groupe, as a provider of identification broker services, must require customers to use digitally signed authentication requests. The digital signature of authentication request must be verified, and only approved requests shall be accepted and forwarded to provider of the electronic identification means.
Consequence for Customers:
Customers not already complying with the obligations of the Traficom regulation must update their service accordingly. Customers must make sure all authentication requests are signed. The signature key must be submitted to IN Groupe to ensure proper configuration. The format of the key must be either i) JWK or ii) URL to JWKS, with KID if required. The update must be in place no later than 31 December 2025.
Note:
Questions can be directed to support.esecurity@nets.eu.
Link to FTN documentation: https://doc.ingroupe.com/developer/finnish-bank-id
Please note that this is an update to the notification sent earlier on 26th June' 2025.
Posted on Aug 01, 2025 - 12:00 CEST
Consequence for IN Groupe:
IN Groupe, as a provider of identification broker services, must require customers to use digitally signed authentication requests. The digital signature of authentication request must be verified, and only approved requests shall be accepted and forwarded to provider of the electronic identification means.
Consequence for Customers:
Customers not already complying with the obligations of the Traficom regulation must update their service accordingly. Customers must make sure all authentication requests are signed. The signature key must be submitted to IN Groupe to ensure proper configuration. The format of the key must be either i) JWK or ii) URL to JWKS, with KID if required. The update must be in place no later than 31 December 2025.
Note:
Questions can be directed to support.esecurity@nets.eu.
Link to FTN documentation: https://doc.ingroupe.com/developer/finnish-bank-id
Please note that this is an update to the notification sent earlier on 26th June' 2025.
Posted on Aug 01, 2025 - 12:00 CEST
Traficom requirement to use digitally signed authentication request Dec 31, 2025 10:00-12:00 CET
This is to inform you that we have received Traficom regulation regrading requirement to use digitally signed authentication request (also called request-object in the OIDC protocol). It is described that the providers of identification broker services must require their customers to use digitally signed authentication request (the so-called request-object in the OIDC protocol).
This means that the digital signature of authentication request is verified and only approved requests are forwarded to provider of the electronic identification means.
Existing e-services must check that the authentication requests comply with the obligations of the Regulation and, if necessary, fix the implementation if the signing of identification requests has not been implemented by 31st December’ 2025.
CONSEQUENCE:
IN Groupe is already compliant with this update. We recommend our customers to ensure that the digital signature of authentication request is verified, and only approved requests are forwarded to us for electronic identification. We, therefore, request you to check that the authentication requests you are sending to us should comply with the obligations of the Regulation and, if necessary, fix this by 31 December 2025.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Posted on Jun 26, 2025 - 15:14 CEST
This means that the digital signature of authentication request is verified and only approved requests are forwarded to provider of the electronic identification means.
Existing e-services must check that the authentication requests comply with the obligations of the Regulation and, if necessary, fix the implementation if the signing of identification requests has not been implemented by 31st December’ 2025.
CONSEQUENCE:
IN Groupe is already compliant with this update. We recommend our customers to ensure that the digital signature of authentication request is verified, and only approved requests are forwarded to us for electronic identification. We, therefore, request you to check that the authentication requests you are sending to us should comply with the obligations of the Regulation and, if necessary, fix this by 31 December 2025.
NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Posted on Jun 26, 2025 - 15:14 CEST
Sunset of Norwegian BankID Signing Service & introducing new BankID signing solution Dec 31, 2025 12:00-14:00 CET
THIS NOTIFICATION APPLIES TO:
Customers of E-Signing
TIMELINE FOR CHANGE:
From: 31.12.2025
DESCRIPTION:
Norwegian BankID BankAxept AS is introducing a new BankID signing service, phasing out the current signing service based on the old ‘BankID Server’ technology. The solution supports signing multiple documents simultaneously and meets the strictest EU requirements for digital signing, qualified signing. IN Groupe is currently implementing this update in collaboration with Norwegian BankID.
CONSEQUENCES:
Customers will need to request a new BankID. All customers will be contacted directly by IN Groupe’s Customer Success team. Importantly, this update will not impact the signing process; customers will continue to experience the same signing flow and receive the same signature output - SDO.
NOTE:
Questions can be directed to support.esecurity@nets.eu
Posted on May 16, 2025 - 13:43 CEST
Customers of E-Signing
TIMELINE FOR CHANGE:
From: 31.12.2025
DESCRIPTION:
Norwegian BankID BankAxept AS is introducing a new BankID signing service, phasing out the current signing service based on the old ‘BankID Server’ technology. The solution supports signing multiple documents simultaneously and meets the strictest EU requirements for digital signing, qualified signing. IN Groupe is currently implementing this update in collaboration with Norwegian BankID.
CONSEQUENCES:
Customers will need to request a new BankID. All customers will be contacted directly by IN Groupe’s Customer Success team. Importantly, this update will not impact the signing process; customers will continue to experience the same signing flow and receive the same signature output - SDO.
NOTE:
Questions can be directed to support.esecurity@nets.eu
Posted on May 16, 2025 - 13:43 CEST