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 to see in advance what the agreement entails.
- Alterations to the Connection Agreement are not permitted. We believe every Service Provider is able to sign the contract as is.
- Don't sign the contract below!
- Send a mail to email@example.com to start the process and receive a copy to sign.
|Version||Template connection agreement|
Template aansluitovereenkomst SURFconext_v1.05_NL + brief.pdf (incl aanbiedingsbrief)
Template Connection Agreement SURFconext_v1.05_EN + brief.pdf (incl accompanying letter)
GDPR (Dutch: AVG) related questions
In the context of transparency we will make the answers to the questions below available for our institutions. This will help them deciding whether or not to connect your service.
|GDPR related questions|
For SURFnet members offering a service, the procedure is as follows:
- 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 firstname.lastname@example.org.
- 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.
Previous versions of the documents on this page can be found below: