LDAP Authentication for F5 Config Backup?

As I prepare to leave what had been my F5's to be taken care of by my replacement.... One of the outstanding issues, is that I hadn't gotten this backup appliance to do LDAP authentication .... preferably the same as the F5's do.

 

It only has AD (which uses python ldap) support, so having it use uid= instead of sAMAaccountName=...shoudn't be that hard. Except I'm not a python programmer....

 

Hopefully some mapping of our F5 group memberships will translate to the backup appliance....thinking/hoping resource administrator == device administrator will suffice. (reserving administrator == administrator....which normally nobody should be in, though it has some remote PS and support accounts in it -- contrary to what first PS had guide me through setting up our 3 vCMP instances on host as vCMP dedicated....the second wanted to have LTM/GTM provisioned on the host, instead of using vCMP instance in DMZ with LTM/GTM/AFM already provisioned. They also blew away our production vCMP which had similar provisioning....and made it LTM/AFM only. And, a frantic couple of weeks to get it working again before the deployment of first new production service....which had a hard deadline to replace old service before EOL date of Windows 2003. Only took me an hour to fix. Meanwhile, the plan for our split DNS now is bluecat to do internal DNS and GTM do external.... Though since nobody here has GTM experience, plans may change to drop GTM.

 

The F5 and DNS falls under the enterprise systems groups, while DHCP is handled by the networking group...which are about to acquire bluecat appliances (to replace aging Sun Fire V240s that currently handle DHCP...its taken a while to have budget to get something.) Seems good if the two groups can work together to have DNS on those appliances as well. (most of which are on aging Sun Fire X4100s.)

 

I think I'll probably miss F5 the most as I move on....