Custom IAM system development
Appfront designs and builds custom Identity & Access Management systems, and integrates existing IdPs such as Microsoft Entra ID, Okta, Auth0, Keycloak, ForgeRock, Ping Identity, AWS Cognito, Google Identity and JumpCloud into your application landscape. Workforce IAM for your employees, CIAM for your customers, federation between domains via SAML/OIDC, MFA roll-outs with passkeys and conditional access, all built around standards such as OAuth 2.1, OIDC, SAML 2.0, SCIM and FIDO2 and aligned with GDPR, NIS2, ISO 27001 and (where relevant) NEN 7510 and DORA.
What is an IAM system?
Identity & Access Management is the combination of processes, policies and software with which an organisation determines which digital identities exist, how they sign in, and what they may then do in which application. In practice it comes down to four closely connected questions: who someone is (identity store and attributes), how you can be sure it is them (authentication, MFA, passkeys, conditional access), what this identity is allowed to do (authorisation, roles, policies, scopes) and how those permissions stay correct over time (lifecycle management, provisioning, de-provisioning, periodic access reviews).
For most organisations, an IAM system is not a standalone application but a layer beneath the entire application landscape. Employees log in to a hundred SaaS tools, partners and customers log in to portals, scripts and services talk to each other via APIs, and in every case it must be clear which identity is involved and which permissions apply. Done well, an IAM system replaces the sprawl of separate passwords, shared accounts and manual permission management with a unified layer that you can steer and monitor centrally and demonstrate in audits.
Appfront builds custom IAM solutions for organisations where an off-the-shelf package no longer fits, and, in other projects, integrates an existing platform such as Microsoft Entra ID, Okta, Auth0, Keycloak, ForgeRock, Ping Identity, AWS Cognito, Google Identity, OneLogin or JumpCloud into a specific application stack. We focus on the technical link, covering single sign-on, federation, provisioning, and role-based and attribute-based access control, and tailor it to your actual organisational structure, security policy and compliance requirements. For projects that go beyond the boundaries of an API platform, we build on our broader API service and our integrations overview page as a starting point for the architecture.
One source for identity
One canonical place for who exists in your landscape, fed from HR, CRM or self-service registration. All applications talk to it via OIDC, SAML or SCIM, so no more separate user tables per tool.
MFA and passkeys
FIDO2/WebAuthn passkeys as the preferred factor, TOTP and push as a fallback, SMS only where it is truly necessary. Conditional access determines per action whether step-up is needed.
Auditable access overview
For every action, you can trace who did it, with which factor, from which device and in which role context. Logs come in a format your SOC or SIEM (Splunk, Sentinel, ELK) can process directly.
Our process for an IAM project
An IAM project stands or falls with good groundwork: which identities exist, which applications are involved, which roles live in HR and in the business, and which compliance requirements bear on the final solution. We work in four phases, with a concrete deliverable after each one that your team can build on, even if you decide after the first phase that an off-the-shelf package is the right route.
We map applications, identities, roles and current login flows. The result: an identity landscape map, a list of gaps in MFA coverage and an initial view on off-the-shelf versus custom.
We design the IAM architecture, choose the primary IdP, define the federation and SCIM routes, and draw up the authentication and authorisation model. Conditional access policies and the choice between RBAC and ABAC also belong here.
Implementation in sprints, with automated tests, integration tests against the applications and a pilot group of real users. We write administration manuals and walk through incident procedures with your IT team.
A phased roll-out per application or user population, with monitoring of login failures, MFA adoption and provisioning errors. After that comes ongoing management, periodic access reviews and further development.
What an Appfront IAM project delivers in practice
Every IAM project is set up around your actual organisation, your application landscape and your compliance requirements. A municipal department, a Dutch healthcare provider, a SaaS company with international customers and a mid-market industrial company will not end up with the same IAM. Below are the building blocks we deliver most often, regardless of the chosen IdP. For each flow, we decide whether to use OIDC, SAML 2.0 or SCIM, depending on what the target application and your primary IdP support.
Single sign-on via OIDC or SAML 2.0
Logging in once at your primary IdP gives access to the entire permitted application landscape. We connect internal tools, SaaS applications and partner portals via OIDC or SAML 2.0, with the right claims, scope mapping and token lifetimes for each application.
MFA roll-out with passkeys
FIDO2/WebAuthn passkeys as the primary factor, with TOTP and push notifications as a fallback. We tie MFA to a conditional access policy, so users are only asked for a stronger factor when the device, location or action justifies it.
SCIM provisioning and deprovisioning
Accounts are created, changed or removed automatically based on a trigger from HR or another source system. Deprovisioning when someone leaves happens within minutes instead of weeks, which is critical for NIS2 and ISO 27001 compliance.
Just-in-time access and PAM
Privileged Access Management with temporary, just-in-time rights instead of permanent admin rights. Administrators request elevated rights for a specific task, with an approval flow, an audit trail and automatic revocation.
Federation between domains
Cross-domain SSO via SAML or OIDC for partners, subsidiaries and merged organisations. A customer logs in to your environment with their own account, with clear agreements on attribute release, session lifetime and de-federation.
Audit trail and SIEM forwarding
Login events, MFA events, role changes and privileged actions end up in a structured audit log that is forwarded to your SIEM (Splunk, Microsoft Sentinel, Elastic). We supply detection rules for typical identity threats alongside it.
IdPs we integrate or replace
Most projects already have an IAM platform in place, sometimes well configured, more often grown organically with legacy configuration. Appfront works with the mainstream IdPs found across the Dutch mid-market and enterprise. For each IdP, we know the quirks in claims mapping, the federation pitfalls and the typical traps in an upgrade project. For healthcare and the public sector, we add DigiD, eHerkenning, UZI cards and eIDAS nodes.
When custom is the right choice
In the vast majority of projects, an off-the-shelf package is the right choice for most of the IAM challenge: Entra ID, Okta or Auth0 cover 80 to 95 per cent of what a typical organisation needs. Custom development comes into play where the package falls short: a specific authorisation rule that is too complex for the policy engine, a legacy system that doesn't speak modern federation, or a CIAM flow that has to keep your customers firmly within your brand experience. Below are four patterns in which we consistently see custom IAM (or a thin custom layer on top of a package) emerge.
Healthcare with BSN, UZI card and patient context
Healthcare organisations work with the BSN (citizen service number) as the personal identifier, UZI cards for care providers and context-aware authorisation: a doctor may only see the record of a patient admitted to their own ward. Context rules like these rarely fit neatly into off-the-shelf RBAC. A custom layer on top of Keycloak or Entra ID, with proper BSN hashing and logging of the treatment relationship, aligns with the GDPR, NEN 7510 and the Wabvpz. See also our NEN 7510 page for the broader context.
B2B2C: your customer has customers of their own
You provide a platform on which your business customer (a SaaS company, a franchisee, a dealer) manages end users of their own. That calls for a multi-tenant identity model with tenant administrators, scope isolation and per-tenant branding of login screens. Auth0 and Cognito can handle part of this, but the finishing touch almost always lies in a custom abstraction layer, which we link to our broader API integration service so that tenant configuration can be managed via API.
Legacy and mainframe alongside a modern IdP
A mainframe, AS/400, AIX application or classic client-server tool speaks neither OIDC nor SAML. For these scenarios, we build a bridging layer: token exchange between a modern IdP and legacy authentication, with an audit trail on both sides. That way, employees benefit from modern SSO and MFA, while the old system keeps its own authentication protocol until it is replaced, at your pace.
Unique RBAC/ABAC rules
Some organisations have rules that can't be captured in a standard policy engine: a combination of role, department, customer segment, geographic working area, contract type and time windows. For those scenarios we build an ABAC (Attribute-Based Access Control) layer that runs alongside the IdP — often with OPA (Open Policy Agent) — so that policies remain declarative, testable and auditable.
Standards we build on
An IAM system that has to last for years relies as much as possible on open standards. That limits vendor lock-in and makes it possible to replace individual components — IdP, MFA provider, directory service — independently of one another when needed. Appfront chooses standardisation over the exotic, and confines custom work to the thinnest layer possible.
OpenID Connect and OAuth 2.1
The modern standard for authentication and delegated authorisation on web and mobile. It works with JWT tokens and PKCE for public clients, and suits SPA, mobile and server-side flows. We build every new application on this unless there is a compelling reason to choose SAML.
SAML 2.0
The de facto standard for enterprise SSO. Many older business SaaS applications, ERP and HRM packages support SAML before they support OIDC. We set up federation between your IdP and those applications, with the right attribute mapping and a certificate rotation plan.
SCIM for provisioning
System for Cross-domain Identity Management is the modern open standard for provisioning and deprovisioning accounts between systems. A new employee in HR automatically lands in your IdP and in the connected SaaS applications — and when they leave, the reverse happens within minutes.
Passkeys with FIDO2/WebAuthn
The W3C standard for phishing-resistant authentication. A passkey on your phone or a hardware key replaces the password-plus-MFA screen. For customer-facing passkeys, they also substantially improve the login UX — a commercial gain on top of the security gain.
eIDAS, DigiD and eHerkenning
For public services and sectors where citizens log in with DigiD, or businesses with eHerkenning at a given assurance level (EH2+, EH3, EH4). We integrate with the DigiD, eHerkenning and eIDAS nodes and make sure attribute handling meets the applicable requirements.
NIS2, ISO 27001 and DORA
NIS2 obliges essential and important entities to implement explicit MFA, least privilege, lifecycle management and logging. ISO 27001 requires a demonstrably managed identity process. For financial service providers, DORA adds requirements around ICT third-party risk — IAM sits right at that intersection. Our ISO 27001 page gives more background.
Security and compliance — with IAM, the starting point, not an afterthought
An IAM system is by definition a security component: it is the gatekeeper of your application landscape. That means security and compliance are not verified at the end of the project, but weigh into every design decision. Appfront works according to OWASP ASVS and the NIST 800-63 guidelines for digital identity. For every new IAM environment we draw up a threat model (STRIDE), determine the privacy impact (a DPIA for sensitive populations such as healthcare or government) and ensure audit logs land in an immutable location. Our broader approach is set out in our information security policy.
In practice, every IAM build includes: secrets in a managed secrets store (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault), certificates with automated rotation, encryption in transit (TLS 1.3) and at rest, and separation of duties between development, acceptance and production environments. For PAM (Privileged Access Management) we use just-in-time access and periodic access reviews; permanent admin rights are the exception, not the rule. For CIAM, we add consent management, right-to-be-forgotten flows and GDPR-compliant attribute management.
For organisations subject to NIS2, we document how MFA coverage is ensured, how lifecycle management is automated, how incidents are detected and reported, and how periodic access reviews are carried out. For healthcare organisations, we align the design with NEN 7510-3 (logging and monitoring), NTA 7516 (secure email) and the guidelines for processing BSN (Dutch citizen service numbers). For financial service providers, we add DORA components covering third-party risk and ICT incident reporting.
Frequently asked questions about IAM
The questions clients ask us most often at the start of an IAM project, and what we typically answer before getting into the detailed design.
IAM stands for Identity & Access Management: the set of processes and software that lets an organisation determine who exists in its digital landscape, how they sign in and what they are allowed to do in which application. An IAM system combines an identity store (where users and their attributes live), authentication (login plus MFA, passkeys, conditional access), authorisation (roles, policies, scopes) and lifecycle management (provisioning, de-provisioning, adjusting access rights when someone changes role).
For classic workforce IAM with standard SaaS applications, a package is by far the best choice. A custom solution comes into play when your use case clashes with what a package can do out of the box: niche CIAM with customer-specific house rules, B2B2C where your customers in turn manage their own customers, healthcare environments with BSN/UZI cards, a legacy mainframe or AS/400 that doesn't fit a standard connector, or unique authorisation rules that require more complex policies than an out-of-the-box engine accepts. Often the right solution is a package for the foundation plus a thin custom layer for the exceptions.
Appfront integrates with Microsoft Entra ID (formerly Azure AD), Okta, Auth0, Keycloak, ForgeRock, Ping Identity, AWS Cognito, Google Identity, OneLogin and JumpCloud. For the public and healthcare sectors, we also integrate with DigiD, eHerkenning, UZI cards and eIDAS nodes. The integration runs via OIDC, SAML 2.0 or SCIM, depending on what the target application and the IdP support.
Workforce IAM manages your own employees' access to internal applications: a closed population whose lifecycle you control yourself. CIAM (Customer IAM) manages your customers' or end users' access to your products: an open population where self-service registration, social logins, passkeys, consent management and scale towards millions of accounts come into play. The technical stack largely overlaps, but the requirements for UX, performance and privacy are fundamentally different. CIAM directly affects your customer experience; workforce IAM is largely invisible to the end user as long as it works.
We build MFA with FIDO2/WebAuthn as the preferred factor by default (passkeys on a phone or hardware key), with TOTP apps and push notifications as fallback options. We only use SMS where legislation or a customer contract requires it, as it is now considered a weak factor. We combine MFA with conditional access rules based on device trust, location, IP reputation and risk signals, and build step-up flows so users are only asked for a stronger factor when the action justifies it. For CIAM, passkeys also deliver a demonstrable conversion gain, as login friction drops measurably.
NIS2 requires essential and important entities to put explicit access measures in place: demonstrable MFA, least privilege, structured lifecycle management, logging and incident response. A well-designed IAM system is the central tool for achieving this. GDPR mainly affects the attribute store (which personal data, on what legal basis) and the retention periods for audit logs. In every project we record which data flows fall under NIS2 and which processing falls under GDPR, so the solution fits your security policy and your record of processing activities. For healthcare organisations NEN 7510 also applies, and for financial service providers DORA.
Yes. Appfront is regularly brought in to review, clean up and professionalise existing Entra ID, Okta, Auth0 or Keycloak environments. We carry out an access review of roles and groups, fix role explosion, map orphaned accounts, revise conditional access policies and set up a working provisioning flow with SCIM where it makes sense. Afterwards we can either hand over management to your own team with clear documentation, or continue to co-manage the environment. A clean-up almost always delivers immediately measurable results: fewer accounts, fewer permanent admin rights, better MFA coverage.
A SOC or security vendor monitors broadly for threats and responds to incidents, and IAM is one of its signal sources (login events, MFA failures, privilege escalation). We focus on building and integrating the IAM layer itself, and make sure the audit logs arrive in a format your SOC and SIEM can process. In a number of projects we work directly with the client's SOC partner to align detection rules with identity signals, such as impossible-travel detection, sudden MFA bypass attempts, or a conspicuous pattern in privileged access requests.
Further reading
Related topics around IAM, API integrations and the broader security and compliance layer that Appfront builds for Dutch mid-market and enterprise organisations.
Talk to us about your IAM project
Tell us what your identity landscape looks like today: which IdP you run, which applications connect to it, which compliance requirements apply (NIS2, ISO 27001, NEN 7510, DORA) and where you experience the most friction. We're happy to help you think through scope, priorities, the choice between off-the-shelf and custom, and the design of the federation, MFA and provisioning layer. A no-obligation first conversation gives you a clear picture of the options and the most stable route: Entra ID, Okta, Auth0, Keycloak or a custom layer on top.
On applatenmaken.com, our platform on custom software development, you will find a deeper look at building IAM software.