Custom eIDAS integration development
Appfront connects your digital service to the Dutch eIDAS node, so that citizens and businesses from other EU countries can log in with their own national eID. We connect you via an accredited eHerkenning broker over the same SAML 2.0 chain as eHerkenning, at the right assurance level. This way you meet your European acceptance obligation and make your service accessible across borders.
What is an eIDAS integration?
eIDAS stands for "Electronic Identification And Trust Services" and is the European regulation that enables mutual recognition of national login methods. A Spaniard with a Spanish eID, a Belgian with itsme or a German with the Personalausweis can therefore log in to a Dutch digital service — without that person having a DigiD. For many government services, accepting these European means is a legal obligation.
In the Netherlands, you don't connect directly to the eIDAS node, but through an accredited broker within the trust framework, which in practice means an eHerkenning broker. The broker is connected to the national node, which is managed under the direction of Logius, RvIG and RVO, among others. Your application communicates with that broker via SAML 2.0: the same technical chain you may already know from eHerkenning or DigiD.
Appfront handles the complete technical connection in line with the eIDAS documentation from Logius and the OWASP ASVS security standard: metadata exchange, PKIoverheid certificates, the SAML flow and the secure processing of the returned identity attributes. We tailor the integration to the required assurance level and to your existing login and user model.
Cross-border eID
Residents and business owners from other EU countries log in with their own nationally recognised eID. Your service receives a verified identity, without the user needing a Dutch DigiD or eHerkenning.
Levels of assurance
eIDAS defines three uniform levels: low, substantial and high. We set up your integration so that the required level is enforced and means authenticated at a lower level are cleanly rejected.
Connecting via a broker
Connecting goes through an accredited eHerkenning broker that is linked to the national eIDAS node. We take care of the SAML metadata, the certificates and the full technical integration with your application.
Our process for an eIDAS integration
We work with a proven method that removes uncertainty early and delivers a stable connection. From an initial analysis of your acceptance obligation and the required assurance level through to go-live and ongoing maintenance, every step is aimed at an integration that your own team can understand and trust.
We map out whether an acceptance obligation applies, which level of assurance your service requires, which identity attributes you need and which broker best fits your situation.
We design the SAML architecture, arrange the connection with the broker, the metadata exchange and the PKIoverheid certificates, and draw up a clear error-handling strategy.
Implementation of the SAML flow and attribute mapping with automated tests, structured logging and monitoring. We test in the chain's pre-production environment before going live.
A controlled go-live with validation of the chain and a safety net, followed by ongoing maintenance, including timely certificate renewal and monitoring of the SAML chain.
What an eIDAS integration delivers in practice
Every eIDAS integration is set up specifically for your service, the required level of assurance and your existing login landscape. Below are the features we deliver most often for organisations that must or want to accept European eID means.
SAML 2.0 connection
A complete SAML 2.0 integration with the accredited broker: signed and encrypted authentication requests, validation of the returned assertion and correct handling of the redirect flow between your service, the broker and the eIDAS node.
Attribute mapping
We securely map the returned identity attributes, such as a unique person identifier, name and date of birth, onto your own user model. This includes linking or matching with an existing account where necessary and permitted.
Level enforcement
Per service, or even per action, we set the minimum required level of assurance: low, substantial or high. Login attempts with a means authenticated at a lower level are rejected cleanly and clearly, with an understandable message for the user.
Certificate & metadata management
Management of PKIoverheid certificates and SAML metadata, with timely alerts and renewal before certificates expire. This prevents your login chain from failing unexpectedly because of an expired key or outdated metadata.
Combining with DigiD & eHerkenning
A single login screen that offers DigiD, eHerkenning and eIDAS side by side. The user chooses their means; your service gets a consistent, verified identity back, regardless of which channel was used to log in.
Logging & error handling
Traceable, GDPR-compliant logging of authentication events in line with the applicable standards frameworks, plus robust error handling for situations such as an aborted login, an invalid assertion or a temporarily unreachable chain, with clear feedback to the user.
Typical use cases in practice
An eIDAS integration works out differently for every organisation. There are a number of contexts we see time and again, and for each of them we have a working setup that takes into account the acceptance obligation, the right assurance level and the connection via an accredited broker.
Government bodies with an acceptance obligation
Municipalities, implementing organisations and other government bodies with a legal obligation to accept recognised European eID means for digital applications. We connect your service to the eIDAS node alongside your existing DigiD and eHerkenning login. See also our software for municipalities and DigiD integration.
Cross-border regional services
Organisations in border regions that serve residents and businesses just across the border — German or Belgian citizens who work, live or run a business in the Netherlands. With an eIDAS integration, they log in with their own trusted national eID, without having to apply for DigiD.
Education with EU students
Universities of applied sciences and universities with international students from other EU countries who need access to digital student services. Through eIDAS — or the related SURFconext federation — they gain access with a recognised identity.
Pensions & insurers
Pension funds, insurers and financial service providers with customers living elsewhere in the EU who want to view their data or policy online. An eIDAS integration at the right assurance level gives these customers secure access to their own file.
Technology we use
An eIDAS integration runs on the SAML 2.0 chain of the trust framework, with PKIoverheid certificates and the message profiles of the recognised broker. We build the backend in the stack that suits you, so your own team can manage or further develop the implementation.
Why Appfront for your eIDAS integration?
Appfront has extensive experience with government and identity integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your acceptance obligation, the required assurance level and your existing login landscape — an integration must not only be technically correct, but also fit the way you work and the requirements of the trust framework.
For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.
You work with a single point of contact who understands both the SAML technology and the rules of the eIDAS chain. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during onboarding.
Also take a look at our related services around eHerkenning integrations, municipality websites, AI for government and custom software. Or get in touch directly for tailored advice.
- Experience with SAML 2.0 and the trust framework (eIDAS, eHerkenning, DigiD)
- Familiar with connecting via a recognised broker to the eIDAS connection point
- Setting up and enforcing the right assurance levels
- Secure by default — PKIoverheid certificates, signing, encryption, scoped permissions
- Structured error handling for aborted or invalid authentications
- GDPR-compliant logging and monitoring of the chain from day one
- Clear documentation that your team can read and maintain
- A single point of contact, no passing you between account managers
- Ongoing management, including timely certificate renewal
- Attention to eIDAS 2.0 and EUDI wallet developments
Security and privacy in eIDAS integrations
A login integration inherently processes personal data: an eIDAS authentication returns a verified identity. The chain itself is built around PKIoverheid certificates, signed and encrypted SAML messages and strict trust agreements between the links. On top of that, Appfront builds in line with the OWASP ASVS: certificates and keys in secure vaults, validation of every assertion and least-privilege access to the identity attributes.
We apply data minimisation and process only the attributes your service genuinely needs. We document the data flows, certificates and attribute mapping so your record of processing activities is complete and you can demonstrably comply with the GDPR. We set up logging in line with the frameworks of the scheme (afsprakenstelsel), so authentication events remain traceable without recording unnecessary data.
More about our approach to security: information security policy and CVD policy.
The integration on this page covers the existing connection point, through which citizens and businesses can reach you using their own national login method. The next step under the same regulation is the digital identity wallet; what you need to accept it is described on Accepting the EUDI wallet in your software.
- GDPR-compliant data processing and minimisation
- PKIoverheid certificates, SAML signing and encryption
- Validation of every returned assertion
- Role-based access and least-privilege principles
- Traceable logging in line with the frameworks
- Monitoring and alerting for chain deviations
- Timely certificate and metadata renewal
- Documentation for your record of processing activities
Frequently asked questions about eIDAS integrations
Answers to the questions we get asked most often about connecting to the eIDAS connection point.
An eIDAS integration lets citizens and businesses from other EU countries log in to your Dutch service with their own national eID. eIDAS is the European regulation on electronic identification and trust services, which enables mutual recognition of national login methods. In the Netherlands, you connect to the eIDAS node via an accredited eHerkenning broker, over the same SAML 2.0 chain as eHerkenning. Users log in with their own country's eID, and your service receives a verified identity at the agreed assurance level.
You need an eIDAS integration when your digital service has to be accessible to residents or businesses from other EU countries. For many government services, there is a statutory obligation to accept recognised European eID means. An integration is also valuable for cross-border regional services, educational institutions with EU students, and organisations such as pension funds and insurers with customers abroad. Together with you, we assess whether an acceptance obligation applies and which assurance levels your service requires.
Dutch service providers do not connect directly, but through an accredited broker within the trust framework, which in practice means an eHerkenning broker. That broker is linked to the national eIDAS node, which is managed under the direction of Logius, RvIG and RVO, among others. Your application communicates with the broker via SAML 2.0, just as with an eHerkenning or DigiD integration. Appfront handles the technical connection: metadata exchange, certificate management, the SAML flow and the processing of the returned identity attributes.
eIDAS uses three uniform European assurance levels: low, substantial and high. The level determines how certain it is that someone really is who they claim to be. Each service has a minimum required level, depending on the sensitivity of the data and the legal framework. A service set to substantial or high accepts only EU means notified at that level or higher. We set up your integration so that the right level is enforced and means notified at a lower level are properly rejected.
The eIDAS chain runs on SAML 2.0, the same standard as eHerkenning and DigiD Machtigen via the routing service. We work with SAML metadata, XML signing and encryption, PKIoverheid certificates and the message profiles of the scheme (afsprakenstelsel). We build the backend integration in the stack that suits you: Node.js, Python, PHP, .NET, Java or Go. We process the attributes that are returned (such as a unique person or organisation identifier) and map them securely to your own user model.
The revised eIDAS 2.0 regulation was formally adopted in 2024 and introduces the European Digital Identity Wallet (EUDI wallet), which is being developed in the Netherlands as the NL Wallet under the direction of the Ministry of the Interior and Kingdom Relations (BZK). The idea is that citizens will soon manage identity data in a wallet and share it selectively. In 2026, the exact rollout, certification and acceptance deadlines were still in flux and partly postponed. We therefore build your integration on the current, production-ready SAML chain and keep an eye on wallet developments for you, so you can connect as soon as that is realistic. Always check the current status at logius.nl.
Yes. The eIDAS chain is built around PKIoverheid certificates, signed and encrypted SAML messages and strict trust agreements between the parties involved. On top of that, Appfront builds in line with the OWASP ASVS: certificates and keys in secure vaults, validation of every SAML assertion, and least-privilege access to identity attributes. We only process the data your service genuinely needs (data minimisation), document the data flows for your record of processing activities, and set up logging that meets the relevant frameworks, so you can demonstrably comply with the GDPR.
Yes. Appfront regularly takes over the management of existing integrations with the trust framework, even if they were originally set up by another party. We review the SAML configuration, the certificates and expiry dates, the attribute mapping and the error handling, document the current setup and draw up a list of improvements. From that point on, we handle changes, extensions — for example a higher assurance level or an additional broker — and monitoring, including timely certificate renewal.
Ready to build your eIDAS integration?
Tell us which service needs to accept European eID means and at which assurance level — we're happy to advise on connecting via a recognised broker, the SAML chain and the combination with your existing DigiD and eHerkenning login. A no-obligation initial conversation will quickly give you a clear picture of the options.