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'

 

Highlighted
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.
Highlighted
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 GARTNER 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

Talend Cloud Developer Series - Introduction

The Talend Cloud Developer Series was created to give you a solid foundational understanding of Talend’s Cloud Integration Platform

Watch Now

Talend Cloud Available on Microsoft Azure

An integration platform-as-a-serviceto help enterprises collect, govern, transform, and share data from any data sources

Watch Now

Self-service Talend Migration: Moving from On-Premises to the Cloud

Move from On-Premises to the Cloud by following the advice of experts

Read Now