ODI Version: 11.1.1.6.5
Agent: Standalone agent on Windows
I have created a new LDAP server in topology. I have an ODI procedure (internally uses Oracle package dbms_ldap) to extract information from the Active Directory. The only information that the ODI procedure uses from the topology is the LDAP username & password. The LDAP host, port are retrieved from a configuration table.
Within the ODI procedure, the LDAP server is setup in the "Command on Source", now when I decrypt the password in target using the API odiRef.getInfo("SRC_PASS"), the password I get is different from the actual password and due to this the LDAP authentication fails. I'm pretty sure that the password entered in topology matches to the actual password.
To workaround this, I used encode.bat to encrypt the password and updated this encrypted password into the work repository table SNP_CONNECT. Now, the ODI procedure runs without any issues. Note: I understand that it is not recommended to update the internal tables, I was only trying this to understand the issue and do not plan to implement this workaround.
Is there any configuration within ODI which sets up a different encryption algorithm just for LDAP? I'm able to decrypt my Oracle database passwords correctly. I'm mentioning this to indicate that there is no mix up in ODI versions and the issue seems to be only with LDAP.