...
- 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. - Technical: standard
Follow the standard connection procedure for SURFconext. When the SP is working, the SURFconext team can enable the desired Level of Assurance in configuration to enable SURFsecureID for your connection. Note that this functionality is available for the SURFsecureID production and test environments, not for the pilot environement. - Technical: special
This is only needed if you need advanced features of SURFsecureID or you use the SURFsecureID pilot 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.
...