ipo one x LDAP integration

[HassanKareem]

Hi all,

I have ipo server edition 9.1.7 I want get contacts from LDAP server I tried some doc, but without benefits.

can any one help me with that??

 

[janni78]

Did you try these docs?

Marketingtools

"Trying is the first step to failure..." - Homer

 

[HassanKareem]

I had try it in health LDAP show available but the contacts does not appear!!

 

[janni78]

I'm assuming you're trying to get contacts from Windows DC?

Username should be DOMAIN\USER, what did you put in Base DN?

"Trying is the first step to failure..." - Homer

 

[Okkie26]

Also you have to do a search in the 'health' screen.

There is no complete list diaplayed here.

 

[HassanKareem]

In 'health' screen the LDAP show available, but in one-x mobile there is no contacts.

 

[HassanKareem]

janni78 Base DN I leave it blank, what should I put it ??

 

[janni78]

You should put the search path of where the contact are in LDAP.

"Trying is the first step to failure..." - Homer

 

[kyle555]

I found that the more deep down the base search in the LDAP was, the faster it went. Searching in dc=customer,dc=com took forever - like a minute after you type a name in your client, it would pop up from Active Directory.

There's a spot in AD where your users are, but the top level of dc=customer,dc=com has too much stuff like PCs in there and it takes a dog's age to find anything doing it that way.

 

[HassanKareem]

Dears,

I have put in

LDAP server URL field : AD server IP.

User : User@company.com

Password : Pass@123


Base DN : DC=company,DC=com
Search Filter: (telephoneNumber=*)


for info My ipo desk phones have integrated, may I use the same settings with one-x ???

 

[derfloh]

That would make sense, wouldn't it?

 

[HassanKareem]

I do it the same settings but it is not working!! in "Health" shows available but the contacts doesn't appear

 

[janni78]

Have you tried looking on the LDAP server logs?

"Trying is the first step to failure..." - Homer

 

[kyle555]

I would refer to my previous comment in this thread! My first kick at the can, it worked but I thought it didn't because it took a whole minute or 3 before any results showed up because the search DN was too broad and included the whole Active Directory - and this was for a small company of a couple of hundred people only.

root your way into the IPO and do something like "tshark -i eth0 port 389 -w /home/Administrator/LDAP.pcap" and try a search in Portal or something. That should write out all your packets on port 389 to a file and you can see what the communication was like between IPO and AD. I found it didn't get to work quick and snappy until I found the right place in AD to search that included only users.

I found a different problem with it not searching if you're not using the default LDAP field mappings. If you set debug level logs in portal, look in

/opt/Avaya/oneXPortal/9.1.400_24/apache-tomcat/logs/1XLDAPDirServiceRollingFile.log
look for "NamingException occurred during LDAP search because: invalid attribute description”

It would appear one-X Portal’s external directory query mechanism takes the exact value from the field mappings and formulates queries from those mappings. In my case, the blank fields the customer entered were used and Portal attempted to formulate queries with them, such as (=*potato*) where every other part of the query had a valid LDAP attribute to the left of the equal sign such as (givenName=potato*).

My customer blanked out some mappings because he didn't want people to be able to lookup home phone numbers. Because of that, searches were being formulated incorrectly by Portal and never hit the AD. So, that's something I'd look at too if I were you