DigiD · eHerkenning · eIDAS · Public sector · Federation
DigiD, eHerkenning and eIDAS for platform builders: what a connector does and what you still arrange
A connector turns DigiD, eHerkenning and eIDAS into standard sign-in for your applications. It does not replace your agreement with Logius or a broker. What the connectors do, which part stays with you, and how to evaluate them.
Where a connector ends and your arrangements begin
- Your agreementWith Logius or an eHerkenning broker, arranged by you
- The connectorDigiD, eHerkenning and eIDAS, included, labelled Beta
- Your applicationsStandard OIDC or SAML sign-in, with a minimum assurance level
On this page
“Supports DigiD” is one of the most overloaded phrases in Dutch public-sector IT. It can mean a finished, running connection to the scheme. It can mean a library you integrate yourself. It can also mean a slide. If you build a platform that citizens, companies or civil servants sign in to, you need to know which one you are buying, and which parts remain yours.
This article separates the two for DigiD, eHerkenning and eIDAS: what a connector does, what HelixIAM includes, and what you still arrange yourself. We label the European eID support Beta, and we explain what that means for how you evaluate it.
What a connector is
DigiD, eHerkenning and eIDAS are not OpenID Connect providers that you point a client at. Each scheme has its own protocol profile, its own assurance levels and its own rules for how a service connects. Your applications, on the other hand, want one thing: a standard sign-in, with a token or an assertion they can verify.
A connector sits between the two. On the scheme side it speaks the scheme’s protocol. On your side it behaves like any other identity source behind a standards-based OpenID Connect and OAuth 2 provider, and a SAML 2.0 identity provider for your existing applications. Your application integrates once with the identity platform, and the scheme-specific work happens behind it.
That is the real value for a platform builder. Without a connector layer, every application team learns the scheme details separately, and every application carries its own copy of the logic. With one, you integrate DigiD once, and a new application is another client of the same platform.
What HelixIAM includes
HelixIAM includes three connectors:
- DigiD, including Machtigen and assurance-level mapping. You connect with your own Logius agreement.
- eHerkenning, for use with your own broker agreement.
- eIDAS, a cross-border sign-in connector.
Each eID connection has a minimum level of assurance that is both requested and enforced. Requesting a level is the easy half: any integration can ask the scheme for one. The point is that the minimum is enforced as well, set once per connection on the platform, so that it does not depend on every application team remembering to check it.
The connectors sit next to the rest of the platform. Single sign-on and single logout work across OIDC and SAML applications. You can broker sign-in from other OIDC, SAML and social identity providers, and connect your existing LDAP or Active Directory, so civil servants and citizens can be served from one identity layer. The signing keys behind your eID connections can be kept in your HSM or Vault.
One more item, labelled as early access: you can sign in with the EU Digital Identity Wallet, tested with the EU reference wallet. It is a separate feature from the three connectors above, and it is not a replacement for them today.
What you still arrange
A connector is software. A DigiD, eHerkenning or eIDAS connection also needs a relationship with the party that operates the scheme. This is the part that no software vendor can do for you, and the part we think should be said first.
- DigiD. You connect with your own Logius agreement. The agreement is between your organisation and Logius.
- eHerkenning. You use your own broker agreement. Which broker you work with is your decision.
- eIDAS. The connector is included. As with the other two, the connection runs under your own arrangements.
- Testing against the scheme. The connector has to be exercised against your broker’s or the scheme’s environment, with your agreement in place. That test is yours to run, and we are glad to join it.
We do not describe the connectors as turnkey, and we do not claim that HelixIAM itself is approved by any of the schemes. Be wary of any pitch that treats the agreement as already taken care of.
If you prefer to use a hub, that works too. Signicat, for example, offers DigiD, eHerkenning and iDIN through its own platform. Because HelixIAM can broker sign-in from other OIDC and SAML identity providers, a hub of that kind can sit behind it, as an alternative to connecting directly. That is a design choice for your architecture, and not one we push either way.
What Beta means here
The European eID support in HelixIAM (DigiD, eHerkenning and eIDAS) is Beta. In our own terms, that means implemented, and still needing validation and your configuration. We have not run a live DigiD round trip against a customer’s agreement.
You should treat that as a design input and not as a footnote:
- Evaluate on your own agreements. Run the connector in your broker’s test environment, with your own settings, before any decision is final.
- Test the assurance levels you need. Check how the minimum level behaves on each connection you configure.
- Decide who owns the evidence. The results of your tests belong in your own assessment, next to your own controls.
For comparison, we found no built-in DigiD or eHerkenning connector in the public documentation of Keycloak. A generic SAML broker might be configured for these schemes, but we have not verified that against the DigiD profile, so we make no claim either way. If you run Keycloak today and want a different route, the question to ask any platform is the same: what exactly does the connector do, and who tested it against what?
One platform for many organisations
Dutch public sector rarely has a single organisation. A regional platform serves several municipalities. A supplier hosts services for many customers. Each of them has its own users, its own branding and its own agreements.
HelixIAM is multi-tenant by design: each tenant gets its own realm, users, keys and branding. A realm per organisation means that one municipality’s connection settings, users and keys are separate from another’s, on a platform you run once. Keys can be taken a step further: a dedicated HSM partition or Vault credential per tenant, and credential-issuer and eID connection keys kept in your HSM or Vault.
The platform itself is self-hosted on your own infrastructure: you decide where data lives, and there is no telemetry. That is not a guarantee of data residency. Where data ends up also depends on the rest of your stack, such as backups and mail relays. It does mean the decision is yours.
What we do not claim
To keep this honest, here is the short list:
- The connectors are Beta, not stable.
- We make no claim of independent testing: an independent penetration test is in preparation.
- We do not offer a conformance or approval statement from any scheme.
- The EU wallet is early access.
- The agreements with Logius or a broker remain with you.
How to start
You do not need to decide everything at once. We suggest three steps.
- A technical demo. Our engineers show the connectors, the assurance-level check and a realm per organisation on a running system.
- Your use case. We map your organisations, your services and the agreements you have or are arranging to a realm layout and a connector set.
- A paid pilot. If it fits, a pilot on your own infrastructure, with success criteria agreed up front, and where you have the agreements in place, a test against your broker’s test environment.
HelixIAM is commercial software from KubeDNA B.V., available under a commercial licence, and it is in early access. We are now onboarding launch partners. If DigiD and eHerkenning are on your roadmap, a demo is a good place to start.