SURFsecureID has three two environments that can be used. The table below shows the differences between these environments.
Image Modified |
---|
Image Removed | Uses production IDP's from SURFconext Image Modified |
---|
- Environment for testing purposes only
- Uses IDP's from SURFconext Test environment
- No contract necessary
- Do not use (privacy) sensitive information
- No strict token registration process is necessary
- Tokens are only valid in the test environment
- No SLA
- No costs
|
For testing the login or registration process with real users (production mode)Holds privacy sensitive information from institutional usersService Providers need follow the proper connection stepsNo strict token registration process is necessaryTokens are only valid in the pilot environmentNo SLANo costsProduction environment |
Connection process for an institution / IDP: - Make sure your (test/acc) IDP is connected to SURFconext test
- Light-weight process for requesting SURFsecureID in test
Connection process for a Service Provider (SP): Connection process for a Second Factor Only service:
| Connection process for an institution / IDP |
:Connection process for a Service Provider (SP):
Connection process for a Second Factor Only serviceImplement the SFO connection to SURFsecureID pilotConnection process for an institution / IDP:
Connection process for a Service Provider (SP): Connection process for a Second Factor Only service:
|
URL's: |
sa-gwauthentication/sa-gwsecondfactoronly/.pilot.pilotgateway.pilot.stepup.surfconext.nl/authentication/Metadata SFO: https://gateway.pilot.stepupsecond-factoronly/URL's:
Self-service registration portal: https://sa.surfsecureid.nlRegistration Authority portal: https://ra.surfsecureid.nl/Metadatasa-gw.surfconext.nl/authentication/Metadata SFO: https://sa-gwsecondfactoronly/