Page History

• 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
• Uses production IDP's from SURFconext Production environment (production mode)
• Holds privacy sensitive information from institutional users
• Service Providers need follow the proper connection steps
• No strict token registration process is necessary
• Tokens are only valid in the pilot environment
• No SLA
• No costs

• Production environment
• Uses production IDP's from SURFconext Production environment (production mode)
• Holds privacy sensitive information from institutional users
• Service Providers need follow the proper connection steps
• Strict token registration process is necessary
• Tokens are only valid in the production environment
• SLA available
• Price Institution is billed based on number of activated tokens. There are no costs for service providers.

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):

• Implement the technical connection to SURFsecureID test
• Register your SP at SURFconext

Connection process for a Second Factor Only service:

• Implement the SFO connection to SURFsecureID test

Connection process for an institution / IDP:

• Light-weight process for requesting SURFsecureID in pilot

Connection process for a Service Provider (SP):

• Follow the contractual part of connecting a service to SURFconext
• Implement the technical connection to SURFsecureID pilot
• Register your SP at SURFconext

Connection process for a Second Factor Only service:

• Implement the SFO connection to SURFsecureID pilot

Connection process for an institution / IDP:

• Formal process for requesting SURFsecureID

Connection process for a Service Provider (SP):

• Follow the contractual part of connecting a service to SURFconext
• Implement the technical connection to SURFsecureID
• Register your SP at SURFconext

Connection process for a Second Factor Only service:

• Implement the SFO connection to SURFsecureID

URL's:

• Self-service registration portal: https://sa.test.surfconext.nl
• Registration Authority portal: https://ra.test.surfconext.nl
• Metadata: https://sa-gw.test.surfconext.nl/authentication/metadata
• Metadata SFO: https://sa-gw.test.surfconext.nl/second-factor-only/metadata

URL's:

• Self-service registration portal: https://sa.pilot.surfsecureid.nl
• Registration Authority portal: https://ra.pilot.surfsecureid.nl/
• Metadata: https://gateway.pilot.stepup.surfconext.nl/authentication/metadata
• Metadata SFO: https://gateway.pilot.stepup.surfconext.nl/second-factor-only/metadata

URL's:

• Self-service registration portal: https://sa.surfsecureid.nl
• Registration Authority portal: https://ra.surfsecureid.nl/
• Metadata: https://sa-gw.surfconext.nl/authentication/metadata
• Metadata SFO: https://sa-gw.surfconext.nl/second-factor-only/metadata