Depending on the integration option you choose for your service, you need to follow a different connection procedure and technical implementation.
An institution must give permission for a SFO integration in the SURFsecureID pilot or production environment. Although an SFO integration is almost always implemented by the institution itself, it is possible that someone else may want to implement it. By requiring permission from the institution we make sure that the proper persons are notified. The SURFconext contactperson (SURFconext-verantwoordelijke) needs to provide this permission by sending an email to firstname.lastname@example.org.
Implement the SFO connection. There is a technical description of how a SFO connection works and what is needed to connect with it. This integration is based on the widely used open standard SAML2, so an integrating can be easily made. However, for some popular systems, we've created a description or even software to make it even easier:
- Procedural / contractual
Because this integration option uses SURFconext for the first factor and privacy sensitive information from the user is transferred to the service, it is necessary to have the correct agreements in place. Make sure you follow the SURFconext contractual obligations. This step is not necessary when you use the SURFsecureID test environment.
Technically, your service will connect to SURFsecureID directly. However, because indirectly your service also uses SURFconext, you will need to register your service in the SURFconext SP dashboard. In this dashboard you must configure a SURFconext Production SP when you want to use the SURFsecureID pilot or production environment. For SURFsecureID test you must configure a SURFconext test SP.
When this is done, you need to implement the technical connection with SURFsecureID. Making this connection is similar to making a SURFconext connection. See also these SAML message examples. These technical steps are the same for each SURFsecureID environment.