tLDAPInput throws an error "Bad search filter" in TAC, while in studio is not

Five Stars

tLDAPInput throws an error "Bad search filter" in TAC, while in studio is not

My job is throwing the error below in TAC, while in studio it is running fine. Could you help me how to fix this? Thank you.

java.lang.Exception: javax.naming.CommunicationException: [LDAP: error code 2 - Bad search filter]; remaining name 'ou=Users,dc=ckoffice,dc=companyko,dc=com'

 

Moderator

Re: tLDAPInput throws an error "Bad search filter" in TAC, while in studio is not

Hello,

Could you please give us more background of your situation? Could you please clarify in which Talend version/edition you are?

Are you using tLDAPInput component with LDAPS(SSL) protocol?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars

Re: tLDAPInput throws an error "Bad search filter" in TAC, while in studio is not

Thank you for your reply Sabrina. The version of my studio is v6.4.1.

Seems like TAC is not accepting a "(objectClass=*)" format although it works on Studio. Instead, it accepts a format like this:
"(&(objectClass=*))"

Tutorial

Introduction to Talend Open Studio for Data Integration.

Definitive Guide to Data Integration

Practical steps to developing your data integration strategy.

Definitive Guide to Data Quality

Create systems and workflow to manage clean data ingestion and data transformation.