2010-03-30 SSSDByDefault

DATE	TIME	WHERE
Tuesday March 30, 2010	ALL DAY	#fedora-test-day (webirc)

What to test?

Today's installment of Fedora Test Day will focus on SSSD by default

If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test with your system and provide feedback.

Who's available

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

Development - Stephen Gallagher, Simo Sorce, Tomas Mraz
Quality Assurance - User:jgalipea, User:zmraz, User:gowrishankar
Design - Máirín Duffy

What's needed to test

A system with a network connection
Fedora 13 (Branched) (tips on installing Branched below) with at least sssd-1.1.0-2.fc13 and authconfig-6.1.2-1.fc13 installed, or a SSSD live image

How to test?

Update your machine

See the instructions on the Branched page on the various ways in which you can install or update to the Branched release. Be sure you are testing with at least authconfig-6.1.2-1.fc13 and sssd-1.1.0-2.fc13. To install the latest authconfig, type: yum --enablerepo=updates-testing update authconfig sssd

Live image

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 with the latest authconfig and sssd packages can be found here.

Test

When ready, please follow each of these test cases:

Don't have an LDAP or kerberos server?
If you do not have a local LDAP or kerberos server to test with, you can still participate. An LDAP and kerberos server are provided during the test day. However, if you are visiting this page well after the test day, the following information may no longer apply.

Public Certificate URL - http://jlaska.fedorapeople.org/sssd/cacert.asc
Available user accounts: sssdtest10001 ... sssdtest10100
Available groups: sssdgroup20001 ... sssdgroup20100
LDAP server information
- Default user password: sssdtest
- ldap_uri = ldap://publictest9.fedoraproject.org
- ldap_search_base = dc=fedoraproject,dc=org
Kerberos server information
- Default user password: sssdkrb5
- krb5_realm = SSSD.FEDORAPROJECT.ORG
- krb5_kdcip = publictest9.fedoraproject.org:88
- krb5_kpasswd = publictest9.fedoraproject.org:749

Report your Results

If you have problems with any of the tests, report a bug to Trac. If you are unsure about exactly how to file the report, 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 James Laska 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, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a link to the bug report for the failure. If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the private LDAP test as you do not have access to an LDAP server), enter the word N/A. In the comments column, you can enter any short, additional information about your testing environment.

Test Results

User	local/local	LDAP/LDAP	LDAP/LDAP TLS	LDAP/Kerberos	Comments
Sample User	none	pass	warn ^[1]	fail ^[2]	↑ Test pass, but also encountered RHBZ #54321 ↑ RHBZ #12345
jlaska	pass	fail ^[1] ^[2]^[3] ^[4]	warn ^[5]	none	↑ Need to fix test case instructions, `ldaps://` didn't work without certificate ↑ RHBZ #578219 - Configuring ldaps:// + cacert does not run cacert_rehash on downloaded certificate ↑ Workaround for bug#578219 - change to tty2 and manually run `cacert_rehash /etc/openldap/cacerts`, then restart sssd ↑ RHBZ #578303 - SSSD users cannot log in through GDM ↑ RHBZ #578311 - authconfig doesn't remember "[X] Use TLS to encrypt connection" setting
liam	fail ^[1]	none	none	none	↑ RHBZ #578124
shanks	pass	fail ^[1]	pass	warn ^[2]	↑ requires a signed certificate in /etc/openldap/cacerts ↑ Unable to change password. "System is offline, password change not possible. passwd: Authentication token manipulation error" message displayed.
duffy	none	warn ^[1]	none	none	↑ RHBZ #578231 - Add checkbox 'Allow authentication via self-signed certificates'
Stephen Gallagher	warn ^[1]	none	none	none	↑ There were issues with the livecd related to setting up local users. After installing the livecd on disk, everything worked as expected.
Lars Delhage	pass	none	none	warn ^[1]^[2]	↑ Make sure your network users use UID:s > 1000, or change min_id in /etc/sssd/sssd.conf. Works fine otherwise. ↑ Couldn't test password changes, because kpasswd service was not available on the server
Sumit Bose	none	none	pass ^[1]	pass ^[2]	↑ Used console login instead of GDM. ↑ Used console login instead of GDM. Couldn't test password changes, because kpasswd service was not available on the server
User	local/local	LDAP/LDAP	LDAP/LDAP TLS	LDAP/Kerberos	Comments

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

[2] RHBZ #12345

[3] Need to fix test case instructions, ldaps:// didn't work without certificate

[4] RHBZ #578219 - Configuring ldaps:// + cacert does not run cacert_rehash on downloaded certificate

[5] Workaround for bug#578219 - change to tty2 and manually run cacert_rehash /etc/openldap/cacerts, then restart sssd

[6] RHBZ #578303 - SSSD users cannot log in through GDM

[7] RHBZ #578311 - authconfig doesn't remember "[X] Use TLS to encrypt connection" setting

[8] RHBZ #578124

[9] requires a signed certificate in /etc/openldap/cacerts

[10] Unable to change password. "System is offline, password change not possible. passwd: Authentication token manipulation error" message displayed.

[11] RHBZ #578231 - Add checkbox 'Allow authentication via self-signed certificates'

[12] There were issues with the livecd related to setting up local users. After installing the livecd on disk, everything worked as expected.

[13] Make sure your network users use UID:s > 1000, or change min_id in /etc/sssd/sssd.conf. Works fine otherwise.

[14] Couldn't test password changes, because kpasswd service was not available on the server

[15] Used console login instead of GDM.

[16] Used console login instead of GDM. Couldn't test password changes, because kpasswd service was not available on the server

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[1]

[1]

[2]

[1]

[1]

[1]

[2]

[1]

[2]

Search

Test Day:2010-03-30 SSSDByDefault

Contents