Bug 187139 - ldapsearch paramaters incorrect
Summary: ldapsearch paramaters incorrect
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: 389
Classification: Retired
Component: wiki
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Orla Hegarty
URL: http://directory.fedora.redhat.com/wi...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-28 19:10 UTC by Mont Rothstein
Modified: 2008-08-11 23:46 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-06-20 21:03:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Mont Rothstein 2006-03-28 19:10:15 UTC
Description of problem:

The ldapsearch parameters, as specified in the final compare accounts section,
do not work with a default install of FDS 1.0.1.

The base dn must be specified and SSL connections are not part of a default
installation.

Version-Release number of selected component (if applicable):

FDS 1.0.1

How reproducible:

Always

Steps to Reproduce:
1.ldapsearch -x -Z '(uid=testuser)'
  
Actual results:

Usage instructions are spit out OR SSL initialization failed error

Expected results:

Search results

Additional info:

The command I used is:

./ldapsearch -p PORT -b "dc=DOMAINNAME,dc=DOMAINEXT" '(uid=testuser)'

Comment 1 Rich Megginson 2006-03-28 19:22:05 UTC
The version of ldapsearch used in those commands is /usr/bin/ldapsearch, which
should be in your PATH by default.

However, in order to use -Z (startTLS), the server and clients must have been
configured to use SSL/TLS - see
http://directory.fedora.redhat.com/wiki/Howto:SSL for more details.  You should
be able to omit the -Z.

Comment 2 Mont Rothstein 2006-03-28 22:49:39 UTC
I realize that -Z can be ommitted, I just thought that most users using this
document would be setup for SSL/TLS and that those who were, would know to use -Z.


Comment 3 Chandrasekar Kannan 2008-08-11 23:46:02 UTC
Bug already CLOSED. setting screened+ flag


Note You need to log in before you can comment on or make changes to this bug.