You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 42 Next »

SURFconext Strong Authentication gives institutions secure access to services. Better security is particularly critical for services handling sensitive data. Such services require stronger forms of authentication than a username and password in order to limit the risk of security incidents.

Institutions can use SURFconext Strong Authentication in two ways:

  1. Institution wide. In this case, SURFconext Strong Authentication is coupled with an existing authentication service (like ADFS). This enables strong authentication for a range of internal and external (cloud)services. This option is also called Second Factor Only.
  2. For a cloudservice connected to SURFconext. Together with the institution, a service provider can enable SURFconext Strong authentication for its service.

SURFconext Strong Authentication gives access to services via three different types of tokens: SMS, Tiqr (smartphone app) or YubiKey (USB hardware token). Users first log in with their institutional account and are then prompted to confirm their identity with their token. In this way there is a second layer of security.

Strong authentication is available at an additional fee for all institutions connected to SURFconext.

How does it work?

  1. The user registers his preferred token (SMS, Tiqr or Yubikey) in the registration portal
  2. User must visit his institution's service desk to have an authorised employee verify his identity.
  3. This employee will bind the user's token to his account. After that the user's token will be activated.
  4. Now the user can log in to any service designated for strong authentication using the two-step login procedure.
  • No labels