4.4. Tokens

4.4.1. 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.
• 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 Key - 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 RADIUS server.
• SMS - A token that sends the OTP value to the mobile phone of the user.
• EMail - A token that sends the OTP value to the EMail address of the user.
• Yubico Cloud mode - A Yubikey hardware that authenticates against the Yubico Cloud service.
• Yubikey AES mode - A Yubikey hardware initialized in the AES mode, that authenticates against privacyIDEA.

The Tokentypes:

• 4.4.1.1. Certificates
  • 4.4.1.1.1. Generating Signing Requests

4.4.2. Token configuration

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

• 4.4.2.1. SMS OTP Token
  • 4.4.2.1.1. First step
  • 4.4.2.1.2. Second step
  • 4.4.2.1.3. HTTP provider
    • 4.4.2.1.3.1. Example:
  • 4.4.2.1.4. Sipgate provider
• 4.4.2.2. Email OTP Token
  • 4.4.2.2.1. First step
  • 4.4.2.2.2. Seconds step
  • 4.4.2.2.3. Configuration Parameters