Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For testing your connection on the SURFsecureID Production or Pilot Gateway you should use use an eduID account instead of one of your regular IdP's accounts.

The second factor authentication tokens that you register in Test , Pilot or Production are separate. You can use the same token and eduID account for Test , Pilot and Production, but you need to do the token registration procedure for each environment that you wish to use.

Warning

If you use your Yubikey with the production environment, you must not use it for any other purpose, including using it with SURFsecureID Pilot or Test. Reusing your production Yubikey is a security risk because Yubikey OTP codes are not tied to the environment.

...

Note
iconfalse

The procedure below applies to the SURFsecureID Production environment. The pilot environment and test and environment have has a different policy. See Pilot environment and Test environment below.

Policy

...

  1. Register an eduID account.
  2. Make sure to complete eduID's verification process for your mail address: this is required for registering a SURFsecureID token.
  3. Go to https://sa.surfconext.nl and login with your eduID account.
  4. Request a second factor authentication token (SMS, tiqr or YubiKey) and complete the self-registration process until step 4 "Activation code'.
  5. Contact us (support@surfconext.nl) for an appointment to finish the registration (ca. 5 minutes). The appointment must be face-to-face, remote vetting is not allowed.
  6. Do not forget to bring/have your activation code and second factor authentication token (SMS, tiqr or YubiKey) and photo ID (passport or drivers license) ready.
  7. After verification SURFnet will activate your token and you can login.

Pilot environment

Policy

  • A SURFnet SRAA will do the vetting of a SP contact. The contact must be available during vetting with their activation code. Vetting using Skype/mail/phone is allowed for the Pilot environments.
  • When the SP contact loses his token, he must register a new token and do the activation process all over again. 
  • eduID accounts are not allowed to have RA(A) rights.
  • eduID IdP is aimed at SPs. SURFnet offers 'best effort support' only.
  • The SP must allow eduID as IdP for their service and is responsible for its own additional authorization rules.

Registration procedure

  1. Register an eduID account.
  2. Make sure to complete eduID's verification process for your mail address: this is required for registering a SURFsecureID token.
  3. Go to https://selfservice.pilot.stepup.surfconext.nl/ and login with your eduID account.
  4. Request a second factor authentication token (SMS, tiqr or YubiKey) and complete the self-registration process until step 4 "Activation code'.
  5. Contact us (support@surfconext.nl) for an appointment to finish the registration (ca. 5 minutes). For the Pilot environment, the appointment can be by telephone or Skype call.
  6. Do not forget to bring/have your activation code and second factor authentication token (SMS, tiqr or YubiKey) ready.
  7. After verification SURFnet will activate your token and you can login.

Test environment

Policy

  • Strictly no policy (wink)
  • This environment is for testing purposes only.
  • There is no assurance for the authentication with this environment.
  • Support is 'best effort'.

Registration procedure

We use the same software in test as in production, and thus need to follow most of the procedural steps. For practical purposes we skip the face to face part of the process. We do however need you to perform an authentication with the token to be activated. This is why we ask you to make an appointment so you can perform the authentication once we initiate the activation of your token from our side.

...