Description
Internal OTP.
Setup
Prerequisites
How to test
Preparation
Log in as the admin:
# kinit admin
Create a user for OTP testing:
# ipa user-add otp --random
Log in as the new user. This will force a password change. This is important since OTP does not yet implement password changing.
# kinit otp
Remember the password you create! It is your first factor.
Enabling OTP
Log back in as the admin:
# kinit admin
Just do it. Otherwise your QR Code won't display properly.
Once your terminal is maximized, enable OTP for the user:
# ipa-testday-otp otp
This command, if successful will print a QR Code to the terminal. Before you do anything else, scan this code using Google Authenticator. This will create a new token in Google Authenticator which you can use to log in. At this point, the user 'otp' can only log in via two factors.
Enabling FAST
Clients which will support OTP, like SSSD, will enable FAST automatically. However, for testing purposes, kinit requires manual configuration.
First, we need to log in as the admin user (or really any user) so that we can use this user's ccache to enable FAST.
# kinit admin # klist
Expected Results
All the test steps should end with the specified results.