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

Highlighted
Six 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.
Six 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=*))"

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog

Talend Cloud Developer Series – Defining Metadata

This video focuses on different methods of adding metadata to a job in Talend Cloud

Watch Now