Get in touch with us. We will plan an introduction meeting. We will tell you about SURFconext, the technology we use, attributes and the necessary contract (and whether a contract is needed in the first place). And of course you can ask us all your questions.
Preparation for this meeting is not required, but these articles will give you a head start:
- What contractual obligations you have differ per customer. Read more about that in the contractual part.
- Dive into SAML or OpenID Connect. You need to support one of these two technologies.
- Get to know attributes and claims.
Publish your application by yourself to our test environment, using via our selfservice Service Provider Dashboard (SP Dashboard).
- Read about & get access to our service SP Dashboard.
- Make sure you have implemented SAML or OpenID Connect on your side. Read our guidelines on how to implement this technology in your application.
- Think about why you need attributes or claims and motivate them properly in the SP Dashboard. Saying 'Needed to identify the user' for every attribute registered doesn't cover the load. We have a minimum disclosure policy and we will review this prior to going to production.
This part consists of the following activities and can be done parallel with testing your service.
- During our introduction you will have learned what what you need to do now. You will either:
- Send us a signed copy of the SURFconext Connection Agreement.
- Or if you are with an institution the 'SURFconext-verantwoordelijke' needs to give permission for your service to be published. We will take care of this.
- Send us a signed copy of the SURFconext Connection Agreement.
- Fill in the GDPR questions in the SP Dashboard.
You have completed Step 3 and you are prepared to go to production and connect. You will do so in the SP Dashboard. Check the following before doing so:
- Give the to be released attributes or claims a last and thorough thought. Use as few as possible! We will discuss this with you if we think this is needed.
- Read our guidelines on how to get an A+ rating in SSL Labs to meet our security measures.
You can register several types of contacts for your service in the SP Dashboard. Fill them and make use of functional addresses that are read by more than you alone. For example: support@yourservice.com.
Institutions don't just connect to any service. In most cases you will have spoken to someone at the institution. Supply us with those contacts we can refer to.
- In the SP Dashboard, tie up the loose ends and add a production entity from the 'service overview' page. After publishing the production entity, a ticket will be created and we will get to work for the last step!
You will need to sit tight at this step of the process. We will send an invite to the institution(s) you have asked us to send an invite to. This can take anything from a few minutes to a few days. Once connected, you will receive a confirmation from us and your service is ready for use!