This page will guide you through any contractual aspects that need to be taken care of prior to connecting your service to the production environment of SURFconext.

Introduction

Every time a user logs in via SURFconext, user-information is transferred from the institution, via SURFconext, to your service. Based on what you agreed, as a Service Provider you may receive data from the Identity Provider/Attribute Provider:

• for the authentication (the proof of authentication by the Identity Provider);
• for authorisation decisions within your service;
• about the group memberships of a user if such is required for cooperation and authorisation within the service provided;
• extra data from a user relevant to the service.

We basically have two situations:

• You are a SURFnet member (an institution): please read here what to check for 
• In other cases, you most likely will need to sign a SURFconext connection agreement, see below.
  • SURFnet does not sign a data processing agreement (DPA, Dutch: verwerkersovereenkomst) with service providers: if a DPA is necessary, that needs to be signed between you as supplier of the service and every institution. 

SURFconext Connection Agreement (Dutch: aansluitovereenkomst)

A contract needs to be signed before  promoting your service to the SURFconext production environment  to document rights and obligations of involved parties. You can download the template linked below to see in advance what the agreement entails. 

See previous versions of the SURFconext Connection Agreement

Anchor
SURFnet_members SURFnet_members

SURFnet members

For SURFnet members offering a service, the procedure is as follows:

1. Check if there is a relevant SURFconext contract.
   If you are registered as a SURFconext Identity Provider (check here), you can assume this is done. In case of doubt, contact support@surfconext.nl.
2. Adhere to the SURFconext Privacy Policy.
3. Inform the person in your organisation responsible for SURFconext (role SURFconextverantwoordelijke) that you are going to connect a service to SURFconext. SURFnet needs explicit consent from the person with this role before your service can be connected.
4. That's it for the contractual part: continue with any other steps left!

Anchor
version-log version-log

Version-log

Previous versions of the documents on this page can be found below:

Navigate

Page Tree
root Documentation for Service Providers searchBox true