7.3. Authentication policies¶
The scope authentication gives you more detailed possibilities to authenticate the user or to define what happens during authentication.
Technically the authentication policies apply to the REST API rest_validate and are checked using Policy Module and Policy Decorators.
The following actions are available in the scope authentication:
7.3.1. otppin¶
type: string
This action defines how the fixed password part during authentication should be validated. Each token has its own OTP PIN, but you can choose how the authentication should be processed:
otppin=tokenpin
This is the default behaviour. The user needs to pass the OTP PIN concatenated with the OTP value.
otppin=userstore
The user needs to pass the user store password concatenated with the OTP value. It does not matter if the OTP PIN is set or not. If the user is located in an Active Directory the user needs to pass his domain password together with the OTP value.
Note
The domain password is checked with an LDAP bind right at the moment of authentication. So if the user is locked or the password was changed authentication will fail.
otppin=none
The user does not have to pass any fixed password. Authentication is only done via the OTP value.
7.3.2. passthru¶
type: bool
If the user has no token assigned, he will be authenticated against the UserIdResolver, i.e. he needs to provide the LDAP- or SQL-password.
Note
This is a good way to do a smooth enrollment. Users having a token enrolled will have to use the token, users not having a token, yet, will be able to authenticate with their domain password.
Warning
If the user has the right to delete his tokens in selfservice portal, the user could delete all his tokens and then authenticate with his static password again.
7.3.3. passOnNoToken¶
type: bool
If the user has no token assigned an authentication request for this user will always be true.
Warning
Only use this if you know exactly what you are doing.
7.3.4. passOnNoUser¶
type: bool
If the user does not exist, the authentication request is successful.
Warning
Only use this if you know exactly what you are doing.
7.3.5. smstext¶
type: string
This is the text that is sent via SMS to the user trying to authenticate with an SMS token. You can use the tags <otp> and <serial>.
Default: <otp>
7.3.6. smsautosend¶
type: bool
A new OTP value will be sent via SMS if the user authenticated successfully with his SMS token. Thus the user does not have to trigger a new SMS when he wants to login again.
7.3.7. emailtext¶
type: string
This is the text that is sent via Email to be used with Email Token. This text should contain the OTP value. You can use the tags <otp> and <serial>.
Default: <otp>
7.3.8. emailsubject¶
type: string
This is the subject of the Email sent by the Email Token. You can use the tags <otp> and <serial>.
Default: Your OTP
7.3.9. emailautosend¶
type: bool
If set, a new OTP Email will be sent, when successfully authenticated with an Email Token.
7.3.10. qrtanurl¶
(TODO): not yet migrated.
type: string
This is the URL for the half automatic mode of the QR token. To this URL the TAN/OTP value will be pushed.
7.3.11. challenge_response¶
(TODO): not yet migrated.
type: string
This is a list of token types for which challenge response can be used during authentication.
