4.4. Tokens¶

4.4.2. Supported Tokentypes¶

At the moment the following tokentypes are supported:

HOTP - event base One Time Password tokens based on RFC4225.
TOTP - time based One Time Password tokens based on RFC6238.
mOTP - time based One Time Password tokens for mobile phones based on an a public Algorithm.
EMail - A token that sends the OTP value to the EMail address of the user.
Four Eyes - Meta token that can be used to create a Two Man Rule.
password - A password token used for losttoken scenario.
Registration - A special token type used for enrollment scenarios (see Registration Code).
Simple Pass - A token that only consists of the Token PIN.
Certificates - A token that represents a client certificate.
SSH Keys - An SSH public key that can be managed and used in conjunction with the Client machines concept.
Remote - A virtual token that forwards the authentication request to another privacyIDEA server.
RADIUS - A virtual token that forwards the authentication request to a RADIUS server.
SMS - A token that sends the OTP value to the mobile phone of the user.
TiQR - A Smartphone token that can be used to login by only scanning a QR code.
U2F - A U2F device as specified by the FIDO Alliance. This is a USB device to be used for challenge response authentication.
Yubico - A Yubikey hardware that authenticates against the Yubico Cloud service.
Yubikey - A Yubikey hardware initialized in the AES mode, that authenticates against privacyIDEA.
Daplug - A hardware OTP token similar to the Yubikey.

The Tokentypes:

Each token type can provide its own configuration dialog.

In this configuration dialog you can define default values for these token types.

Token Configuration: SMS