It is a separate web application within Freja ID which serves for token import, management and basic troubleshooting.
With Freja SSP, a web portal for user enrolment and provisioning, users can provision their own tokens. Otherwise, an administrator has to enter each token number as a directory attribute manually.
OATH compliant tokens can be used assuming the associated PSKC file is available. Sending the PSKC file to Verisec will allow us to check compatibility.
As a backup option, a one-time password delivery by SMS or e-mail can be used until the user receives a new token.
Yes, Freja ID can be linked to as many calling systems as desired, as well as user data repositories (e.g. Internet bank user directory and internal user directory). It has a RADIUS interface which is the standard used by most secure remote access systems, and a SOAP interface that would normally be used for web applications such as an internet banking system.
a. In such cases, Freja ID can be configured/instructed to perform 2FA authentication via SMS or Email.
b. The token can be temporarily suspended*, which will trigger the alternative (SMS or e-mail) authentication in Freja.
If Freja ID is configured for the migration scenario, yes, you can.
You’re free to use any tokens you wish, as long as they are OATH compliant. You don’t have to purchase tokens from Verisec.