AD LDAP Authentication in HPOO 10.10

[DBR]

We have LDAP working in 9.x but I can't get it working in 10.10.  Does anyone have a mapping of the terms used in 9.x to those used in 10.10? 

This is the error I am getting.

Verify that your configurations are correct.

Thanks!

Don

[Sussan_Z_OO]

Hello DBR,

I am an Operations Orchestration Support representative and I will be researching your question. Please allow me a bit of time to provide an answer.

Thank you!

sussan

[Sussan_Z_OO]

Hello DBR,

Regarding your question I have found an image that could help you, please take a look the image>>

I hope this answer help you.

Kind Regards,

sussan Z.A

[DBR]

Sussan,

That did not help plus that screen shot is from 10.x not 10.10. It has changed in 10.10.

Thanks,
Don

[Sussan_Z_OO]

Hello Don,

I hope you are great, regarding your question I found some information that could help you, please take a look:

Add an Active Directory LDAP authentication configuration (pag40 (OO10.10 Central_Guide.pdf))

OO Version 10.10 Releease Notes.pdf >>
Note: For each client certificate, you need to define a user, either an internal user or LDAP user. The name of the user should be defined in the certificate attributes. The default is value of the CN attribute. See the Processing a Certificate Principal section for more details.
Note that even if HP OO is set up with multiple LDAP configurations, it is only possible to
authenticate the user using the client certificate attributes with the default LDAP. Central will first try to authenticate the user with the default LDAP, and if this fails, will try to authenticate within the HP OO internal domain.

Upgrading to HP OO 10.10 from HP OO 9.x >>
If the filter contains one user name, this user name is taken.
For example, if the User filter is (&(objectClass=person)(sAMAccountName={0})), the User ID attribute is sAMAccountName.

If the filter contains 0 or more than one user name, the User ID attribute will be one of the following: n sAMAccountName, if the LDAP is Active Directory n uid, otherwise

For example, if the filter is (&(objectClass=person)(|(sAMAccountName={0})(uid={0}))),
then the User ID attribute will be sAMAccountName if the LDAP is Active Directory and uid, otherwise.

I hope this information resolve your issue, but if it doesn’t, please let me know so I can continue with the research and involve more resources in this thread.

PD: I have attached you the pdf documents.

Thanks for your patience and cooperation on this case.
Best Regards,

Sussan Z.A

[Sussan_Z_OO]

Hello Don,

I hope you are having a great week.

Regarding this thread and the last email, I have continued my researches and I found in the document OO10.10_Api_Guide.pdf, where you can find the next topics related with the LDAP/AD > configuration, please take a look:

•   LDAP Configuration
•   Create a New LDAP Configuration

-          In this topics you can to configure the LDAP/AD, following their instructions (Descriptions)

I hope this information answer your question if not, don't doubt to let me know and I will involve more resources to help you.

Kind Regards,

Sussan Zamora

[Sussan_Z_OO · Accepted solution]

Hello,

If you find that this or any post resolves your issue, please be sure to mark it as a accepted solution.
Thank you
Sussan Zamora
HP-OO