Implementation issues with new software going through F5 load balancer

Just consider that I'm not talking about direct access to everything, just the DC communication. I'm assuming there's another (application) server somewhere in this equation that is the endpoint of all of this, and that the DC is only needed for authentication requests. If at all possible, it would be easiest to allow application traffic through the F5 and have the client software talk to the DC directly. If the client is a non-Windows, non-domain member piece of software that is capable of Kerberos authentication, then it's still technically possible to route this traffic through a proxy, but you still need DNS resolution, a path for port 88 Kerberos traffic, and probably a keytab or two accessible to the software.

Just out of curiosity, does the application support any other form of authentication, like Basic?