[
https://issues.apache.org/jira/browse/DIRSERVER-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584925#comment-16584925
]
Emmanuel Lecharny commented on DIRSERVER-2246:
----------------------------------------------
Sorry, but I don't understand.
The trace you attached just show a user doing a bind ({{uid=phone,
ou=utenti,dc=smabit}}) followed by a search:
* baseDN: ou=contatti,dc=smabit
* scope: ONE
* filter: (ObjectClass=*)
* attributes: ObjectClass
* control: PageResultsControl, size=100
The response you get is one single entry, {{cn=Jesco Köller+commonName=Jesco
Köller,ou=contatti,dc=smabit}}, with 4 {{ObjectClass}}, {{top}}, {{person}},
{{organizationalPerson}}, {{inetorgPerson}}
There is nothing about cn, jpeghoto or telephone number stripulated in this
request.
Also note that the request uses the same cn twice, which is quite useless.
Is that a request that works ?
Also if you don't specify any attribute in your search request, you'll get all
the entry's attributes in return. if you add attributes that aren't present in
the entry, the server will simply ignore them but return the found entry.
At this point, I would need more context about what you exactly try to do, and
how you do it...
> DS does not answer search request which contains attribute jpegPhoto
> --------------------------------------------------------------------
>
> Key: DIRSERVER-2246
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2246
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 2.0.0-M24
> Reporter: Peter Hoyer
> Priority: Major
> Attachments: trace.pcapng
>
>
> I am trying to connect a Snom with with an Apache DS LDAP server.
> The problem is that the phone, if you do not specify any additional
> parameters, will include the attributes cn, telephoneNumber, jpegPhoto in the
> serach. Result is that the server does not answer the search request at all.
> Is there any way to convince the server to ignore unknown attributes in the
> search request?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)