Open
Bug 106904
Opened 24 years ago
Updated 3 years ago
Enable "Find" button in the ldap server properties dialog
Categories
(MailNews Core :: LDAP Integration, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: bugzilla, Unassigned)
References
Details
It would really really help if there was a "test" button in the LDAP setup in
the prefs. This way a lot of problems could be avoided.
Comment 1•23 years ago
|
||
We already have a find button (which is disabled right now) in the ldap server
properties which should list all the base dn for that server.
I have started working on enabling the find button.
Changing summary to reflect that.
mcs, if I am using the following url to find the base dns on the server
"nsdirectory.netscape.com". I get only one result "dc=com"
ldap://nsdirectory.netscape.com/?namingcontexts?base?(objectclass=*)
I know there are more one base dns on this server.
Do you know why I am getting only one result.
Is there any other way to find the base dn's
Status: NEW → ASSIGNED
Summary: Need "test" button in LDAP setup → Enable "Find" button in the ldap server properties dialog
Comment 2•23 years ago
|
||
Reading the namingContexts is about the best you can do... what makes you think
all the entries on nsdirectory are not under dc=com? I suspect they are.
You could look for VLV indexes or do a one level search under the namingContext
if only one is returned.
Comment 3•23 years ago
|
||
What I meant to ask was how to get the entries under dc=com.
I tried the one level search and I got zero results.
How do I look for VLV indexes?
Thanks.
Comment 4•23 years ago
|
||
*** Bug 148781 has been marked as a duplicate of this bug. ***
Comment 5•23 years ago
|
||
To find what is beneath dc=com, a one-level search based at dc=com should work
(it does for me; an anonymous search returns 3 entries). Note that while the
namingContexts attribute in the root DSE will probably always be readable
without authenticating, in the general case other searches may return no results
due to lack of authentication, etc.
There is no standard for discovering what VLV searches are supported. In a
Netscape or Sun ONE DS, you can find the DNs of entries that describe the
configured VLV searches in the vlvsearch attribute in the root DSE. Each of the
entries pointed to contains this kind of info:
dn: cn=Surnames,cn=config,cn=ldbm
objectclass: top
objectclass: vlvSearch
cn: Surnames
vlvbase: dc=com
vlvscope: 2
vlvfilter: (sn=*)
Comment 6•23 years ago
|
||
We could potentially use the LDAP RDF datasource to allow users to select a
sub-tree to search under. However, I'd argue that just allowing them to select
from the naming contexts is going to be sufficient in most cases (it'll even
work for AOL-TW, though the choice it makes will be suboptimal). I wouldn't
object to just doing the simple case now, and leaving the extra functionality
for the future.
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
QA Contact: grylchan → ldap-integration
| Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
Assignee: srilatha → nobody
Status: ASSIGNED → NEW
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•