Test Day:2015-03-12 Ipsilon: Difference between revisions

Latest revision as of 19:37, 26 June 2015

Fedora Test Days

Ipsilon

Date	2015-03-12
Time	all day

Website	Fedora Calendar
IRC	#fedora-test-day (webirc)
Mailing list	test

Can't make the date?
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?[edit]

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..

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Development - Rob Crittenden (rcrit), Patrick Uiterwijk (puiterwijk), Simo Sorce (simo), Nathan Kinder (nkinder)
QA - Mike Ruckman (roshi)

Prerequisite for Test Day[edit]

At least three virtual (or physical) machines will be required to test.

Recommendation is 1GB RAM and 4GB free disk post-install per-VM (a 10GB disk for the IDP/IPA and an 8 GB disk for each of the SP is fine).

Working DNS is required. It can be configured during the test.

You'll also need Fedora 22 Alpha.

How to test?[edit]

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[edit]

If you're running Fedora 22, make sure you have all the current updates for it installed, using the update manager.

Configure the COPR repo[edit]

A few last-minute changes were made to the packages for the Test Day. Run:

# dnf copr enable rcritten/ipsilon

to enable the repository containing the needed packages before you begin testing.

Permissive SELinux[edit]

There are some known issues with SELinux at the moment. Please put each VM into permissive mode before proceeding with testing:

# setenforce permissive

At the completion of testing it would be great to get the output of:

# ausearch -m AVC -ts recent

for each VM.

Test Cases[edit]

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:

Test login/logout to SP

Info plugin testing:

Test retrieving additional attributes

Attribute mapping and filtering:

Map and filter attributes

Test Results[edit]

If you have problems with any of the tests, report a bug to Bugzilla usually for the component ipsilon. 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.

If you get an Internal Server error on an SP then include in the bug report any errors you might find in /var/log/httpd/ssl_error_log.

If you get an Internal Server error on the IDP then include in the bug report any errors you might find in /var/log/httpd/error_log.

Please include as much detail as you can on the steps taken to cause any exceptions.

User	Install IPA	Install IDP	Install SPs	Login/out to SP	Info Plugins	Attribute Mapping and Filtering	References
Sample User	none	none	none	pass	warn ^[1]	fail ^[2]	↑ Test pass, but also encountered RHBZ #54321 ↑ RHBZ #12345
mrniranjan	pass	pass	pass	warn ^[1]	pass	pass	↑ Logins pass but after logout and login back auth form doesn't come up instead it shows authenticated!
simo	pass	pass	pass	warn ^[1]^[2]^[3]	pass	pass	↑ kdestory to test password based re-login ↑ sometimes password-based re-login leaves me stranded in the Idp and does not redirect back - https://fedorahosted.org/ipsilon/ticket/74 ↑ Clicking on LogOut in the SP when user is already logged out in the Idp, gives a 400 - Bad Request in the Idp
spoore	pass	pass	pass	warn ^[1]	pass	pass	↑ same results as simo above
nkinder	pass	pass	pass	warn ^[1]^[2]	pass	pass	↑ IdP initiated logout does not trigger SLO - https://fedorahosted.org/ipsilon/ticket/87 ↑ SP logout without an active session results in a 400 page - https://fedorahosted.org/ipsilon/ticket/88 (also encountered by simo and spoore above)
Roshi	pass	pass	pass	none	none	none

[1] Test pass, but also encountered RHBZ #54321

[2] RHBZ #12345

[3] Logins pass but after logout and login back auth form doesn't come up instead it shows authenticated!

[4] story to test password based re-login

[5] sometimes password-based re-login leaves me stranded in the Idp and does not redirect back - https://fedorahosted.org/ipsilon/ticket/74

[6] Clicking on LogOut in the SP when user is already logged out in the Idp, gives a 400 - Bad Request in the Idp

[7] same results as simo above

[8] IdP initiated logout does not trigger SLO - https://fedorahosted.org/ipsilon/ticket/87

[9] SP logout without an active session results in a 400 page - https://fedorahosted.org/ipsilon/ticket/88 (also encountered by simo and spoore above)

[1]

[2]

[1]

[1]

[2]

[3]

[1]

[1]

[2]

@@ Line 19: / Line 19: @@
 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)
+* Development - [[User:rcritten|Rob Crittenden]] (rcrit), [[User:puiterwijk|Patrick Uiterwijk]] (puiterwijk), [[User:simo|Simo Sorce]] (simo), [[User:nkinder|Nathan Kinder]] (nkinder)
+* QA - [[User:Roshi | Mike Ruckman]] (roshi)
 == Prerequisite for Test Day ==
@@ Line 25: / Line 26: @@
 At least three virtual (or physical) machines will be required to test.
-Recommendation is 1GB RAM and 4GB free disk post-install per-VM.
+Recommendation is 1GB RAM and 4GB free disk post-install per-VM (a 10GB disk for the IDP/IPA and an 8 GB disk for each of the SP is fine).
 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:
+You'll also need [https://getfedora.org/en/server/prerelease/ Fedora 22 Alpha].
-* An updated [http://fedoraproject.org/get-prerelease Fedora 22 pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
 == How to test? ==
@@ Line 51: / Line 50: @@
 === '''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 [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
+If you're running Fedora 22, make sure you have all the current updates for it installed, using the update manager.
+=== '''Configure the COPR repo''' ===
+A few last-minute changes were made to the packages for the Test Day. Run:
+ # dnf copr enable rcritten/ipsilon
+to enable the repository containing the needed packages before you begin testing.
+=== '''Permissive SELinux''' ===
+There are some known issues with SELinux at the moment. Please put each VM into permissive mode before proceeding with testing:
+ # setenforce permissive
+At the completion of testing it would be great to get the output of:
-=== '''Live image''' ===
+ # ausearch -m AVC -ts recent
-Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
+for each VM.
 == Test Cases ==
@@ Line 68: / Line 83: @@
 SAML SP testing:
-# [[QA:Testcase_ipsilonv1_ipa_login|Test login/logout to SP]]
+* [[QA:Testcase_ipsilonv1_ipa_login|Test login/logout to SP]]
 Info plugin testing:
-# Test retrieving additional attribute
+* [[QA:Testcase_ipsilonv1_sssd_info|Test retrieving additional attributes]]
 Attribute mapping and filtering:
-# Map and filter attributes
+* [[QA:Testcase_ipsilonv1_attr_map_filter|Map and filter attributes]]
-FAS SP testing:
+== Test Results ==
-# Test login/logout of SP using FAS auth
+If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=22&component=ipsilon ipsilon]. 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
-== Test Results ==
+If you get an Internal Server error on an SP then include in the bug report any errors you might find in {{filename|/var/log/httpd/ssl_error_log}}.
-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 get an Internal Server error on the IDP then include in the bug report any errors you might find in {{filename|/var/log/httpd/error_log}}.
-If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
+Please include as much detail as you can on the steps taken to cause any exceptions.
 {|
 ! User
-! [[QA:Testcase_sample_1|Sample test 1]]
+! [[QA:Testcase_ipsilonv1_ipa_install|Install IPA]]
-! [[QA:Testcase_sample_2|Sample test 2]]
+! [[QA:Testcase_ipsilonv1_ipa_idp_install|Install IDP]]
-! [[QA:Testcase_sample_3|Sample test 3]]
+! [[QA:Testcase_ipsilonv1_sp1_install|Install SPs]]
-! [[QA:Testcase_sample_4|Sample test 4]]
+! [[QA:Testcase_ipsilonv1_ipa_login|Login/out to SP]]
+! [[QA:Testcase_ipsilonv1_sssd_info|Info Plugins]]
+! [[QA:Testcase_ipsilonv1_attr_map_filter|Attribute Mapping and Filtering]]
 ! References
 |-
 | [[User:SampleUser|Sample User]]
 | {{result|none}}
+| {{result|none}}
+| {{result|none}}
 | {{result|pass}}
 | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
@@ Line 103: / Line 122: @@
 | <references/>
 |-
-|}
+|-
+| [[User:mrniranjan|mrniranjan]]
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|warn}} <ref>Logins pass but after logout and login back auth form doesn't come up instead it shows authenticated!</ref>
+| {{result|pass}}
+| {{result|pass}}
+| <references/>
+|-
+|-
+| [[User:simo|simo]]
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|warn}} <ref>kdestory to test password based re-login</ref><ref>sometimes password-based re-login leaves me stranded in the Idp and does not redirect back - https://fedorahosted.org/ipsilon/ticket/74</ref><ref> Clicking on LogOut in the SP when user is already logged out in the Idp, gives a 400 - Bad Request in the Idp</ref>
+| {{result|pass}}
+| {{result|pass}}
+| <references/>
+|-
+|-
+| [[User:spoore|spoore]]
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|warn}} <ref>same results as simo above</ref>
+| {{result|pass}}
+| {{result|pass}}
+| <references/>
+|-
+|-
+| [[User:nkinder|nkinder]]
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|warn}} <ref>IdP initiated logout does not trigger SLO - https://fedorahosted.org/ipsilon/ticket/87</ref><ref>SP logout without an active session results in a 400 page - https://fedorahosted.org/ipsilon/ticket/88 (also encountered by simo and spoore above)</ref>
+| {{result|pass}}
+| {{result|pass}}
+| <references/>
+|-
+| [[User:Roshi|Roshi]]
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| <references/>
+|-
+|-|}
-[[Category:QA Templates]]
+[[Category:Fedora 22 Test Days]]

Search