Bug 785902
| Summary: | Errors with empty loginShell and proxy provider | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Stephen Gallagher <sgallagh> |
| Component: | sssd | Assignee: | Stephen Gallagher <sgallagh> |
| Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3 | CC: | apeetham, grajaiya, jgalipea, jzeleny, prc |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | sssd-1.8.0-2.el6.beta2 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: The function which was storing user entities to SSSD cache didn't check for empty strings in loginShell attribute. Therefore if it encountered such attribute, the storing procedure would fail completely.
Consequence: When using proxy provider and utilized nss module returned empty loginShell, updating user record in cache failed. Therefore invalid data could have been returned to client.
Fix: Make sure that proxy provider doesn't pass empty string to the function.
Result: when proxy provider gets result with empty loginShell attribute, it doesn't fail and user is stored correctly. Therefore valid entry is returned to the client.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 11:54:35 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Stephen Gallagher
2012-01-30 21:01:04 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: The function which was storing user entities to SSSD cache didn't check for empty strings in loginShell attribute. Therefore if it encountered such attribute, the storing procedure would fail completely.
Consequence: When using proxy provider and utilized nss module returned empty loginShell, updating user record in cache failed. Therefore invalid data could have been returned to client.
Fix: Make sure that proxy provider doesn't pass empty string to the function.
Result: when proxy provider gets result with empty loginShell attribute, it doesn't fail and user is stored correctly. Therefore valid entry is returned to the client.
Verified on sssd-1.8.0-22.el6.x86_64. The beaker output for the associated automation script is given below: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: Verify BZ release ticket #342 :- Errors with empty loginShell and proxy provider :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ PASS ] :: Running '/usr/bin/ldapadd -x -D cn=Manager,dc=example,dc=com -w Secret123 -H ldap://hubcap.lab.eng.pnq.redhat.com -f /tmp/tempuser.ldif > /dev/null 2>&1' :: [ PASS ] :: Running '/sbin/service sssd stop' :: [ PASS ] :: Running 'rm -f /var/lib/sss/db/*' :: [ PASS ] :: Running '/sbin/service sssd start' :: [ PASS ] :: Running '/bin/sleep 5s' :: [ PASS ] :: Running '/usr/bin/id tempuser' :: [ PASS ] :: File '/var/log/sssd/sssd_PROXY.log' should not contain '\[sysdb_set_entry_attr\] (6): Error: 14 (Bad address)' :: [ PASS ] :: File '/var/log/sssd/sssd_PROXY.log' should not contain '\[sysdb_store_user\] (6): Error: 14 (Bad address)' :: [ PASS ] :: File '/var/log/sssd/sssd_PROXY.log' should not contain 'Internal Error (Cannot make/remove an entry for the specified session)' :: [ PASS ] :: Running '/usr/bin/ldapmodify -x -D cn=Manager,dc=example,dc=com -w Secret123 -H ldap://hubcap.lab.eng.pnq.redhat.com -f /tmp/deluser.ldif > /dev/null 2>&1' :: [ PASS ] :: Running 'rm -f /tmp/tempuser.ldif' :: [ PASS ] :: Running 'rm -f /tmp/deluser.ldif' :: [ LOG ] :: Duration: 34s :: [ LOG ] :: Assertions: 12 good, 0 bad :: [ PASS ] :: RESULT: Verify BZ release ticket #342 :- Errors with empty loginShell and proxy provider Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0747.html |