Page History

SURFsecureID has three two environments that can be used. The table below shows the differences between these environments.

Image Modified

Image Removed

WarningThe pilot environment is deprecated

	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

Uses production IDP's from SURFconext

(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
Institution is billed based on number of activated tokens. There are no costs for service providers.

Connection process for an institution / IDP:

Connection process for a Service Provider (SP):

Connection process for a Second Factor Only service:

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. Note that the "technical: standard" option is not available for the pilot environment.
Register your SP at SURFconext

Connection process for a Second Factor Only service: