How do I configure Active Directory LDAP attributes for OTM to use 1

[Woodro]

I have OTM 2.1 with LDAP to an Active Directory. I don't understand AD but I do know you have to have the attributes mapped from OTM to the AD. Only I'm not getting anything back from AD. The test connection confirms a good link between OTM and LDAP but I can't pull anything across. When I do a "get attribute" in OTM nothing happens. Does AD attributes have to be defined with in AD so that OTM's mapping of the attributes will work? If so how do you define those attributes in AD. The IT guy here doesn't know what he's doing with AD, he is new to it and so am I. Thank you in advance.


Woodro

 

[sandyml]

Be very careful with making changes to the Active Directory; you can easily trash your entire network. What you are doing with OTM is mapping to existing attributes in Active Directory.

 

[I2007]

Do you run a win 2003 server?

 

[I2007]

I mean, is the 2003 server the prime AD.

 

[Woodro]

Yes, their AD does run on 2003 server. Problem, in the "bind to" field of the LDAP setup on OTM I used a user name and password of the administrator of the AD listed in the AD directory. When I hit the "test connection" button on the LDAP setup box it bombs out. If I use a different entry, lets say a user that doesn't even have admin rights, the connection tests fine. Even with a connection that tests OK It still won't bring in the attributes to OTM. Thats why I thought the problems got to be with AD. The NTP shows examples of Search Root(o=company.com),I used what was showing in the AD for this. The bind to server as: I used the administrators user id and pass and it didn't work but if I used a regular user it worked. The ntp shows uid=OTM,ou=people,0=company.com. Do I have to use the OTM password? I'm stuck.

Thanks,


Woodro

 

[Woodro]

O' and yes I do believe that the Ad is the prime.

Woodro

 

[I2007]

I asked becuase win2003 initially closes services and you have to open them when you need them. I had the same problem with a TAPI server connecting to a win2003 AD, but I had to get special hotfixes to the client machines, becuase of the encryption level in AD contra the clients. Connection seemed fine but I couldn't access services on the AD.

A another thing you have to check. Is the OTM a member of the domain. Then you have to create a new admin user locally on the OTM machine and use that user to log on the OTM. Then you have to create that user a admin user on the domain and as a local admin user on the AD.

I found theese hotfixes in knowledgebase at microsoft.com

hope this was a little helpfull???

i2007

 

[Woodro]

Thanks for your input but we finely solved the riddle yesterday. The problem was that the example in the NTP shows the "bind to statement" as uid=OTM,ou=people,o=company.com and gives no instruction on how to find that information on Active Directory. The IT guy found a share ware program that breaks down the LDAP configurations on a report and it lists all the attributes that are filled in on the AD plus the bind to information. In my case it was a string of CN=xxx and DN=xxx statements not the cu= and o= statements they show in the NTP. And your right about the Domain stuff. We had our user name and pass built on both OTM and the AD. So that part is working now. One thing though? If you have a mapp field not filled in with an attribute and you highlight that field and push the "get attribute" button. Is the OTM suppose to be able to pull in the attribute to that field and populate the box with the attribute automaticly or just give you the complete list of attributes to choose from in the drop down list?

Woodro

 

[I2007]

I'm not sure really, sorry.

But another thing:
quote: The IT guy found a share ware program that breaks down the LDAP configurations on a report and it lists all the attributes that are filled in on the AD plus the bind to information

What program was this???

i2007

 

[Woodro]

Sintera LDAP brouser. I'm not sure on the exact spelling but that is what the IT dept gave me. It seems like there was another LDAP information program that MS makes too. I've got it written down out at the job site and I'll send that one to you later.

Woodro