Hide Forgot
Description of problem: The "ldap_uri" section of sssd-ldap man page does not specify the valid formats ( hostname, IPv4 or v6 address and a port number) Version-Release number of selected component (if applicable):sssd-1.5 How reproducible: NA Steps to Reproduce: NA Actual results: NA Expected results: ldap_uri section in man sssd-ldap includes it's usage. For example, The URIs can be a hostname (for example, ldapsrv.example.com), a dotted-decimal IPv4 address (for example, 10.65.210.1), or a colon-separated IPv6 address enclosed in square brackets (for example, [fc00:abc::100]) followed by an optional port number (preceded by a colon) port 389 is used if not specified(for example: ldapsrv.example.com:1024).
sorry, I forgot to add ldap:// in the examples
Valid URI formats are now specified in SSSD-LDAP(5): <snip> The format of the URI must match the format defined in RFC 2732: ldap[s]://<host>[:port] For explicit IPv6 addresses, <host> must be enclosed in brackets [] example: ldap://[fc00::126:25]:389 </snip> Verified in version: # rpm -qi sssd | head Name : sssd Relocations: (not relocatable) Version : 1.5.1 Vendor: Red Hat, Inc. Release : 52.el6 Build Date: Tue 20 Sep 2011 09:11:03 PM IST Install Date: Mon 26 Sep 2011 05:56:30 PM IST Build Host: x86-010.build.bos.redhat.com Group : Applications/System Source RPM: sssd-1.5.1-52.el6.src.rpm Size : 3550647 License: GPLv3+ Signature : (none) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> URL : http://fedorahosted.org/sssd/ Summary : System Security Services Daemon
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 SSSD man page did not explicitly list the rules for encoding IPv6 IP addresses. IPv6 addresses must be escaped in square brackets. Consequence: users confused when plain unescaped IPv6 addresses did not work Fix: an example and pointer to RFC 2732 was added Result: happy users
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-2011-1529.html