Versions Compared

Old Version 1

changes.mady.by.user Peter Clijsters

Saved on

compared with

New Version 10

changes.mady.by.user Pieter van der Meulen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update medata URLs of the test en production environments. These are now published at metadata(.test).surfconext.nl

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

Image Modified

Image Modified

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

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


Connection process for an institution / IDP:

Connection process for a Service Provider (SP):

Connection process for a Second Factor Only service:


URL's:

sa-gw
authentication/
sa-gw
second
factor
only/

URL's:

URL's:

sa-gw
authentication/
sa-gw
second
factor
only/