Closed
Bug 244755
Opened 22 years ago
Closed 20 years ago
the filter field in the LDAP server "advanced" tab doesn't seem to be used
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: sxpert, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
I have an LDAP directory with the following structure
dn: cn=x xx,ou=people,dc=xxx,dc=fr
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
cn: x xx
sn: xx
givenName: x
mail: xxx@xxx.fr
this person may have several posix accounts
dn: uid=xx,cn=x xx,ou=people,dc=xxx,dc=fr
objectClass: top
objectClass: account
objectClass: posixAccount
cn: x xx
uidNumber: 0
gidNumber: 0
homeDirectory: /home/xx
userPassword:: [hidden]
uid: xx
when using the filter feature "(objectClass=inetOrgPerson)", I get multiple
records per user, one for the inetOrgPerson record, and one for each posixAccount
Reproducible: Always
Steps to Reproduce:
1. create ldap server with the above structure, and one or more posix account
per person
2. try to show that ldap server in mozilla
3. curse
Actual Results:
shows :
x xx
x xx xxx@xxx.fr
Expected Results:
should only show one record, as in
x xx xxx@xxx.fr
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•21 years ago
|
Assignee: sspitzer → mail
Comment 1•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•