| Fedora Test Days | |
|---|---|
| |
| Features/FreeIPA_Two_Factor_Authentication | |
| Date | 2013-06-06 |
| Time | all day |
| Website | QA/Fedora_19_test_days |
| IRC | #fedora-test-day (webirc) |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's instalment of Fedora Test Day will focus on FreeIPA Two Factor Authentication.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Nathaniel McCallum (npmccallum)
- Development - Rob Crittenden (rcrit)
- Development - Martin Kosek (mkosek)
Feedback
We need your feedback!
- Talk to us on #freeipa on freenode
- Send as an e-mail.
- Log issues and enhancements in trac or Bugzilla.
Prerequisite for Test Day
- A live image. Tips on using a live image are available at FedoraLiveCD.
| Architecture | SHA256SUM |
|---|---|
| x86_64 | TODO |
| i686 | TODO |
Please make sure that the LiveCD has enough memory to operate. We recommend:
- At minimum 2.5 GB of memory for non-graphical run
- At minimum 3 GB memory for graphical (GNOME) run
- Fedora 19 prepared with the following instructions:
# cd /etc/yum.repos.d
# wget http://repos.fedorapeople.org/repos/npmccallum/freeipa-otp/fedora-freeipa-otp.repo
# cd /usr/sbin
# wget http://npmccallum.fedorapeople.org/freeipa-otp/ipa-testday-otp
# wget http://npmccallum.fedorapeople.org/freeipa-otp/ipa-testday-radius
# yum update
# yum install freeipa-server freeipa-client sssd python-qrcode python-pyrad
Test Cases
Install/Setup Tests:
Test Results
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.
| User | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|
| Sample User |  |
 |
 |