Cause: SSSD had no facility for comparing the contents of the 'authorizedHost' attribute of a user to the hostname on the client system.
Consequence: Users of SSSD could not take advantage of the functionality in pam_ldap provided by the pam_check_host_attr option.
Change: SSSD added a new feature and option to the LDAP access_provider, allowing users to enable the behavior of pam_check_host_attr.
Result: SSSD users can now set the 'ldap_access_order = host' and 'ldap_user_authorized_host' options to enable access-control based on the presence of this attribute in LDAP.
DescriptionJ.H.M. Dassen (Ray)
2011-11-21 10:51:01 UTC
3. What is the nature and description of the request?
Need to have sssd check the user's host attribute, similar to how nss_ldap
"pam_check_host_attr yes" config worked.
4. Why does the customer need this? (List the business requirements
here)
Currently there is no way to configure host-based access control without
involving IPA. Customer would have to revert back to pam_ldap or maintain
their own sssd package.
5. How would the customer like to achieve this? (List the functional
requirements here)
Backport the patch from https://fedorahosted.org/sssd/ticket/746https://fedorahosted.org/sssd/changeset/3612c73e7957721bcbf31d0118e2ac210eb46b88
6. For each functional requirement listed in question 4, specify how
Red Hat and the customer can test to confirm the requirement is
successfully implemented.
Configure sssd.conf with access_provider=ldap and ldap_access_order=host.
Verify that sssd checks the host attribute in the user's ldap entry to
determine access privilege.
7. Is there already an existing RFE upstream or in Red Hat bugzilla?
Fixed upstream through <https://fedorahosted.org/sssd/ticket/746>.
8. Does the customer have any specific timeline dependencies?
RHEL 6.3
9. Is the sales team involved in this request and do they have any
additional input?
No
10. List any affected packages
sssd
11. Would the customer be able to assist in testing this
functionality if implemented?
Yes
Comment 11Stephen Gallagher
2012-06-12 13:08:45 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: SSSD had no facility for comparing the contents of the 'authorizedHost' attribute of a user to the hostname on the client system.
Consequence: Users of SSSD could not take advantage of the functionality in pam_ldap provided by the pam_check_host_attr option.
Change: SSSD added a new feature and option to the LDAP access_provider, allowing users to enable the behavior of pam_check_host_attr.
Result: SSSD users can now set the 'ldap_access_order = host' and 'ldap_user_authorized_host' options to enable access-control based on the presence of this attribute in LDAP.
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
3. What is the nature and description of the request? Need to have sssd check the user's host attribute, similar to how nss_ldap "pam_check_host_attr yes" config worked. 4. Why does the customer need this? (List the business requirements here) Currently there is no way to configure host-based access control without involving IPA. Customer would have to revert back to pam_ldap or maintain their own sssd package. 5. How would the customer like to achieve this? (List the functional requirements here) Backport the patch from https://fedorahosted.org/sssd/ticket/746 https://fedorahosted.org/sssd/changeset/3612c73e7957721bcbf31d0118e2ac210eb46b88 6. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Configure sssd.conf with access_provider=ldap and ldap_access_order=host. Verify that sssd checks the host attribute in the user's ldap entry to determine access privilege. 7. Is there already an existing RFE upstream or in Red Hat bugzilla? Fixed upstream through <https://fedorahosted.org/sssd/ticket/746>. 8. Does the customer have any specific timeline dependencies? RHEL 6.3 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages sssd 11. Would the customer be able to assist in testing this functionality if implemented? Yes