|Fedora Test Days|
What to test?
Today's installment of Fedora Test Day will focus on Ipsilon. Ipsilon is a server and a toolkit to configure Apache-based Service Providers. The server is a plugable self-contained mod_wsgi application that provides federated SSO to web applications. User authentication is always performed against a separate Identity Management system (for example a FreeIPA server), and communication with applications is done using a federation protocol like SAML, OpenID, etc..
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - rcritten:Rob Crittenden (rcrit), puiterwijk:Patrick Uiterwijk (puiterwijk), simo:Simo Sorces (simo), nkinder:Nathan Kinder (nkinder)
Prerequisite for Test Day
At least three virtual (or physical) machines will be required to test.
Recommendation is 1GB RAM and 4GB free disk post-install per-VM.
Working DNS is required. It can be configured during the test.
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
- An updated Fedora 22 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
How to test?
Ipsilon has a number of different components. Multiple virtual machines (or physical machines if you'd prefer) will be necessary to test.
Testing will involve:
- Installing an identity source (IPA)
- Installing an Identity Provider (IDP)
- Installing one or more Service Providers (SP)
- Testing login and logout between those service providers using a browser.
In an effort to reduce the number of VM's required IPA and the IDP will be installed on the same server.
Each SP will be enrolled as an IPA client.
See below for specific details.
Update your machine
If you're running Fedora 22, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Install/Setup Tests (initially SAML):
- Install IPA server
- Install IDP
- Install first SP
- Install an SP on another VM using the same instructions as above
SAML SP testing:
Info plugin testing:
- Test retrieving additional attribute
Attribute mapping and filtering:
- Map and filter attributes
FAS SP testing:
- Test login/logout of SP using FAS auth
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|