Forum Discussion
Progress! fumbling my way thru VPE, so now I understand the process of creating the variable assign action, and I have this working successfully using ldap over port 389 to my AD server. I am now attempting to get it to work using ldaps over 636... I followed the same process I used for converting my ldap auth server to ldaps, creating a new AAA server, using a pool, with one address, specifying ldaps, port 636, and then created the virtual server with a server ssl profile to do the encryption. I suspected a cert issue, so I went with the insecure-compatible ssl profile for testing, before I got into the process of getting the cert from our AD team and importing into the LTM. However that made no difference, APM still reports that it is unable to connect to the newly defined LDAP server. A tcpdump shows that the ldaps call goes out the external interface, gets to the AD server passes 2800 bytes of data, and the LTM then sends a Reset to close the connection.... Ideas?