SAML federation Education & research eduGAIN-ready

SURFconext integration development

Appfront connects your application as a Service Provider to SURFconext, SURF's federation hub for Dutch education and research. Students, teachers and researchers at connected institutions can log in to your app with their own institutional account. We handle the full SAML implementation, attribute processing, testing on MujinaIdP and support with the SURF onboarding through to production release.

What is a SURFconext integration?

SURFconext is the Dutch federation hub for education and research, managed by SURF. It connects hundreds of Dutch education and research institutions with each other and with external applications. A student, teacher or researcher logs in with their own institutional account and gains access to connected external apps, from learning platforms to research tools and library environments.

For you as an application owner, this means one SAML integration with SURFconext, and all connected institutions can use your app. There is no need for a separate integration per university or university of applied sciences, as SURFconext handles the federation. You can also enable eduGAIN to be discoverable by academic institutions abroad.

Appfront builds according to the official SURFconext developer documentation, the SURF standards framework and the OWASP ASVS security standard. We tailor attribute processing, session handling and test scenarios to your use case, so that onboarding with SURF runs smoothly and the integration remains maintainable.

SP

One integration, all institutions

A single SAML integration with SURFconext gives you access to hundreds of connected education and research institutions in the Netherlands. After onboarding, your app automatically appears in the SURFconext catalogue and can be requested by any connected institution.

staff student org entitlement

Attribute-based authorisation

eduPerson attributes such as eduPersonAffiliation (student/employee/alumnus), schacHomeOrganization and eduPersonEntitlement control access rights in your app. We map them correctly in line with the SURFconext attribute release policy and GDPR principles.

eduGAIN worldwide

Through SURFconext, you are automatically reachable by other academic federations around the world via eduGAIN. Researchers and students from abroad can log in with their own institutional account, without you having to build a separate integration for each federation.

Our onboarding process for SURFconext

We work to a proven methodology that takes into account both the technical SAML implementation and the SURF onboarding process. From an initial analysis of your application and user roles through to production release and ongoing maintenance, every step is aimed at an integration that remains maintainable in the long term.

1
Analysis & scope

We map out which eduPerson attributes your application needs, which user roles exist, and whether Strong Authentication or VOOT groups are relevant.

2
Architecture

We design the integration architecture, choose the right authentication and draw up an error-handling strategy.

3
Development

Implementation with automated tests, structured logging and monitoring. You see working builds along the way.

4
Go-live & maintenance

A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development.

What a SURFconext integration delivers in practice

Every SURFconext integration is set up specifically for your application and target audience. Below are the components we most often deliver for Service Providers joining the SURF federation.

Service Provider registration

We prepare the SAML SP metadata, configure the entity ID and Assertion Consumer Service (ACS) URLs, and create certificates set up for rotation. We handle the application to SURF, work through the test phase and support you through to production release.

Attribute processing

Correctly mapping eduPerson attributes to your internal user model: eduPersonAffiliation for roles (student, employee, alumnus), schacHomeOrganization for institution, eduPersonEntitlement for entitlements. Including just-in-time provisioning at first login.

Strong Authentication

For higher-risk apps, such as assessment systems, financial apps or research data containing privacy-sensitive information, we set up SURFconext Strong Authentication (SFO). Users then authenticate with MFA via their institution's IdP or SURFsecureID.

VOOT groups & Invite

Group management via VOOT or SURFconext Invite for multi-institution collaborations. Ideal for project teams in which researchers, lecturers or students from multiple institutions work together, and where guest users from outside SURFconext are invited.

Account linking & JIT provisioning

For apps with their own local user store, we make sure the SURFconext identity is correctly linked to existing or new user records. Just-in-time provisioning automatically creates an account at the first successful login, including the right role based on eduPerson attributes.

Test environment via MujinaIdP

Before your app goes live in the SURFconext production environment, we test it thoroughly against MujinaIdP, SURF's test framework in which we can simulate different user roles, attributes and scenarios. This makes the production release predictable and free of surprises.

Typical use cases in practice

A SURFconext integration typically appears in a handful of recognisable scenarios. For each of them we have a working setup, with specific attention to attribute release, session handling and onboarding.

EdTech vendors

SaaS products for education, from learning platforms and assessment tools to digital study environments and skills apps, reach hundreds of Dutch educational institutions through SURFconext with a single integration. See also our custom software development.

Research platforms

Platforms for research collaboration, data management and publishing use SURFconext plus eduGAIN to give researchers worldwide access with their own institutional account. Attribute-based access control determines which datasets or tools are accessible per role or institution.

Library & content providers

Library systems, academic publishers and content suppliers link their access system to SURFconext so that students and researchers get direct access to journals, e-books, databases and repositories, without a separate login for each service.

Inter-institutional collaboration

Consortia, joint degrees and sector-wide projects in which staff and students from multiple institutions work together. With VOOT groups and SURFconext Invite you manage these multi-institution groups centrally, with scoped access to shared apps and documentation.

Technology we use

We build SURFconext integrations with the standard SAML 2.0 and OIDC stacks that suit your application, together with testing on MujinaIdP. The exact choice depends on your framework and preferences, so that your own team can manage or further develop the integration.

If your service targets primary, secondary or vocational education rather than higher education, there is our Entree Federatie integration.

SAML 2.0 OpenID Connect (OIDC via SURFconext) SimpleSAMLphp Shibboleth SP mod_auth_mellon Spring Security SAML Passport-SAML (Node.js) PySAML2 OmniAuth SAML (Ruby) eduPerson attribute schema schacHomeOrganization eduGAIN interfederation MujinaIdP test framework SURFsecureID / SFO VOOT for groups XML signing & encryption

Why Appfront for your SURFconext integration?

Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes, because an integration must not only be technically sound but also add practical value to the way you work.

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 dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also take a look at our broader services around API integrations, middleware, custom software and web app development.

  • Experience with SAML Service Provider implementations and SURFconext onboarding
  • Understands eduPerson attributes and the SURF attribute release policy
  • Familiar with MujinaIdP test scenarios and production releases
  • Attention to attribute minimisation and GDPR in an education context
  • Structured error handling and retry mechanisms
  • Extensive logging and monitoring from day one
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance and proactive further development
  • An approach tailored to your existing IT landscape

Security and privacy in SURFconext integrations

A federation integration handles the personal data of students, teachers and researchers. Appfront builds in line with the SURF Normative Framework and the OWASP ASVS. Among other things, that means attribute minimisation (only the eduPerson attributes that are genuinely needed), signed and, where necessary, encrypted SAML assertions, correct single logout (SLO) and careful certificate management with scheduled rotations.

SURFconext complies with the SURF Normative Framework and Dutch privacy legislation. We document which attributes are requested and why, so your record of processing activities is complete and you can demonstrate compliance with the GDPR. For student records and other special categories of data, we make the appropriate assessments in consultation with your Data Protection Officer.

More about our approach to security: information security policy and CVD policy.

  • GDPR-compliant data processing and minimisation
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least-privilege principles
  • Audit logs with traceable data flows
  • Automatic retry and dead-letter queues
  • Monitoring and alerting for anomalies
  • Secrets management following best practices
  • Documentation for your record of processing activities

Frequently asked questions about SURFconext integrations

Answers to the questions we get asked most often about SURFconext Service Provider connections.

A SURFconext integration connects your application as a Service Provider (SP) to SURFconext, SURF's federation hub for Dutch education and research. Students, teachers and researchers at connected institutions can log in to your app with their own institutional account. An integration typically covers SAML 2.0 metadata exchange, attribute handling (eduPersonAffiliation, schacHomeOrganization, eduPersonEntitlement), testing via MujinaIdP, and finally the production connection to SURF.

SURFconext is relevant when your application is used by Dutch educational institutions or research organisations: EdTech platforms, research tools, library or journal environments, collaboration portals and policy apps. With a single SAML integration to SURFconext, you reach hundreds of institutions without having to set up a separate federation for each one. For international institutions outside the Netherlands, eduGAIN provides a broader federation.

The technical implementation of a SAML Service Provider is usually completed within a few weeks, including testing on MujinaIdP. On top of that comes the SURFconext connection process itself: registering as an SP, supplying metadata, going through the test phase and coordinating the production release with SURF. Allow a few extra weeks for that formal process, depending on lead times at SURF and at the first connected institutions.

Depending on your stack, we work with SAML libraries such as SimpleSAMLphp, Shibboleth SP, mod_auth_mellon, Spring Security SAML, Passport-SAML or PySAML2. We do our testing with MujinaIdP (SURF's testing framework). We tailor eduPerson attribute mapping, just-in-time provisioning and session handling to your application. For OIDC integrations via SURFconext, we use the standard OIDC libraries of your framework.

The cost is determined by the complexity of the data flows, the number of systems to be integrated, the required synchronisation frequency and the amount of custom business logic. Ongoing maintenance, monitoring and support also affect the total investment. We always provide a clear quote after a no-obligation analysis of your situation.

Yes. SURFconext complies with Dutch privacy legislation and the SURF Normative Framework. Appfront builds in line with the OWASP ASVS and applies attribute minimisation: we only request the eduPerson attributes your app genuinely needs. SAML assertions are encrypted and signed where necessary, and single logout (SLO) is implemented correctly. For special categories of personal data (such as student records), we make the appropriate assessments in consultation with your Data Protection Officer.

Yes. Appfront regularly takes over the management of existing SURFconext integrations, even when they were originally built by another party. We review the SAML configuration, attribute mapping, session handling and certificate management, document the current setup and draw up improvement proposals. From that point on, we can handle changes, extensions and monitoring, including timely certificate rotation.

SURFconext is designed specifically for the Dutch education and research landscape. Typical use cases: EdTech vendors offering their app to Dutch universities, universities of applied sciences, vocational colleges (MBO) or research institutes; research platforms and data tools that need to be widely accessible; library and journal access systems; collaboration portals for inter-institutional projects; and access to international services via the eduGAIN federation.

Ready to connect your app to SURFconext?

Tell us which application you want to connect and which user roles and attributes go with it. We're happy to advise on the SAML setup, attribute release, testing on MujinaIdP and onboarding with SURF. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.

Edit content