Symantec Access Management

  • 1.  Wrong syntax of LDAP search filter in SMPS Logs

    Posted May 14, 2018 08:57 AM

    Hi People,

     

    We are getting the below error in SMPS Logs.

     

    Although there is no user impact.

     

    [4604/140506757588736][Tue May 08 2018 19:47:54][SmDsLdapProvider.cpp:1883][ERROR][sm-Ldap-00650] CSmDsLdapProvider::Search(): Wrong syntax of LDAP search filter: (&(|(objectclass=inetOrgPerson)(objectclass=organizationalPerson)(objectclass=person))("Identity mapping Attribute"=))

    [4604/140506757588736][Tue May 08 2018 19:47:54][SmDsLdapProvider.cpp:1883][ERROR][sm-Ldap-00650] CSmDsLdapProvider::Search(): Wrong syntax of LDAP search filter: (&(|(objectclass=inetOrgPerson)(objectclass=organizationalPerson)(objectclass=person))("Identity mapping Attribute"=))

     

    Version of PS:12.7

     

    Thanks,

    Alok



  • 2.  Re: Wrong syntax of LDAP search filter in SMPS Logs

    Broadcom Employee
    Posted May 14, 2018 10:06 AM

    Alok, There was a discussion almost a year ago on this topic, see if it's helpful:

    Wrong syntax of LDAP search filter 

     

    You may also check this KB, https://comm.support.ca.com/kb/wrong-syntax-of-ldap-search-filter/kb000053772 

    to see if related.

     

     

    best wishes.- Vijay



  • 3.  Re: Wrong syntax of LDAP search filter in SMPS Logs

    Posted May 14, 2018 10:17 AM

    Yes.
    But I have checked that link.

    But in my case there is no space in the SMPS logs.

     

    Thanks.

    Alok



  • 4.  Re: Wrong syntax of LDAP search filter in SMPS Logs

    Broadcom Employee
    Posted Jul 12, 2018 08:04 PM

    Most likely it is due to the double quotes in ("Identity mapping Attribute"=) . 

     

    If your searches are not failing and you do require the use of special characters, the KB linked earlier for the EnableSearchFilterCheck can be used to remove the messages from the log.



  • 5.  RE: Re: Wrong syntax of LDAP search filter in SMPS Logs

    Posted Sep 21, 2020 04:54 PM
    Was there a resolution to this? I am facing same error, with no space on the ldap filter. I notice that the filter does not contain username. Any help is much appreciated.