Encoded space character ( %20) allowed in Base DN for a LDAP Organization

Products

• CA Strong Authentication

Issue/Introduction

At AA version 9.1, customers successfully used an encoded space character (%20) in Base Distinguished Name (as shown below), that is, users were then successfully retrieved via AA Admin Console. But at AA version 9.1.03, customers are unable to retrieve users via AA Admin Console if encoded space character (%20)  used in Base Distinguished Name. The error seen in the arcotadmin.log is "LDAP error code 32 with data code 0".

Note that Note LDAP error code 32 with data code 0 (data 0) can be caused by the "Defined DN does not exist". Error 32 usually means, the referenced object does not exist. I.e. You provided a bad DN value for something that needed a correct DN value.

Environment

Release : Advanced Authentication 9.1.3

Cause

A bad DN value provided for something that needs a correct DN value.

Resolution

Do not use an encoded space character (%20) in the Distinguished Name.

Additional Information

None.