LDAP between OXE and and an LDAP server

[aquarius_DUP]

Hello,
• Please help me to find the reason of unsuccessful LDAP communication between our OXE system in Lab and an LDAP server. All the necessary (appropriate) configuration has done well related to LDAP configuration in OXE. Furthermore the maintenance command (>client_ldap) doesn’t work as well. Does somebody know any other possibility to test LDAP communication? If so, please write it in a reply.

Thanks in advance

[Eliott_DUP]

Alcatel-Lucent forgot to deliver client_ldap with R8 ...
This command is available since R8.0.1 g1.503.9 again (crms00058274)
You could capture your LDAP communication using tcpdump -s 1500 -w /tmpd/capture.cap and analyze it with Wireshark.
There are also some corrections for A4059 Attendant and LDAP.
Which exact SW versions do you use?
Does it work for normal stations?

[cavagnaro]

And what does this has to do with Attendant???

[Eliott_DUP]

Not sure. The attendant can use LDAP too - but I think he picked the wrong forum...

[cavagnaro]

Moving...

[aquarius_DUP]

Gentlemen,

We managed to fix our LDAP problem.
During sniffing what happens on the communication it turned out that OXE does not authenticate itself at LDAP Bind! I mean OXE does not send the user principal name what I set at the user identification field (ldapsearch@kfki.com).
When I modified the user identification field to LDAP distinguished name (insted of user principal name) (cn=ldapsearch, ou=..., dc=...) it worked!
It seems OXE checks the beginning of the User Identification field and it must start with "cn=" (see attached screenshot)

Documentation does not provide me the right format of this field!
For me it's not trivial to use LDAP dn instead of user principal name (UPN).

Best regards,
Sándor

LDAP.doc

[cavagnaro]

Thanks for your contribution I know other users will like this.

[aquarius_DUP]

Dear members,

Unfortunately it comes up against difficulty to use canonical format regarding active directory (LADAP).
Does anybody know what is to be done in OXE configuration to work it?
For example it is a number in active directory: +36 46 333333.
I mean how is it possible to define + character in OXE or what can we do to be translated a number received from LDAP sever in canonical format?

Regards,
Sándor

[Eliott_DUP]

Read TG0005 - Chapter 4.3 => Country code
Does it help?

[aquarius_DUP]

Thanks Eliot,

Unfortunately the BPWS is closed right now. So I will check it!

Regards,
Sándor