We are using APEX on standalone ORDS behind an F5 load balancer, and our goal is to enable Windows Integrated Authentication (Kerberos/NTLM) so users can log in to APEX using their existing Windows domain credentials without entering a username/password.
We understand that standalone ORDS does not support IWA directly and that a reverse proxy (Apache/IIS) may be required to handle Windows authentication and pass the authenticated username to APEX through a trusted header.
We are looking for guidance or best‑practice recommendations on how to implement Windows Integrated Authentication for APEX in this architecture, including any required reverse proxy configuration and APEX authentication scheme setup.