For testing with the SURFsecureID test environment you need a user account. If you do not have access to an identity provider (IdP) that is connected to the SURFconext test environment, you can use eduID. EduID is an IdP that allows anybody to create an account.

For testing your connection on the SURFsecureID Production 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 or Production are separate. You can use the same token and eduID account for Test and Production, but you need to do the token registration procedure for each environment that you wish to use.

Production environment

Policy

SURFnet adheres to a strict policy for using eduID for SURFsecureID:

• A SURFnet SRAA will do the vetting of a SP contact. The contact must be physically present with his token, activation code and ID. Skype/mail is not allowed for the Production 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://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.

Test environment

Policy

• Strictly no policy 
• 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.

1. Register an eduID account.
2. Make sure to complete eduID's verification process of your mail address: this is required for registering a SURFsecureID token.
3. Go to https://sa.test.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 TEST environment, the appointment can be by telephone or Skype call, chat or email. You do NOT have to visit us.
6. Do not forget to bring/have your activation code and second factor authentication token (SMS, tiqr or YubiKey) ready, you will need it during the activation process. The activation code is shown in step 4 of the registration process, and is sent to you by email.
7. After verification SURFnet will activate your token and you can then use it login at LoA/level 2 or above.

Until you have activated your token, you can only use the account to authenticate at LoA 1. SFO authentication always requires an activated token.

Attributes

The following attributes are available when using a eduID account. Whether you actually receive these attributes depends on the attribute release policy (ARP) that is configured for your SP in SURFconext: