Forum Discussion
Kerberos Authentication Failing for Exchange 2016 Behind F5 Cloud WAF
- Oct 25, 2025
To enable authentication externally via XC/WAF, configure F5 APM to use Entra ID (or another external IdP) for user auth via SAML or OAuth, instead of negotiating NTLM/Kerberos at the front end — since the WAF will interfere with that exchange.
Once APM consumes the SAML/OAuth token, it can extract the user’s identity and use Kerberos Constrained Delegation (KCD) to request service tickets (TGTs) and present them to Exchange on behalf of the user.
APM acts as the SAML SP for Entra ID and uses Kerberos Constrained Delegation to grab tickets on behalf of the user.
If you haven’t seen it, check out the lab below — it walks through the F5 APM ↔ Entra ID ↔ KCD setup step-by-step:
https://clouddocs.f5.com/training/community/iam/html/class1/module3/lab01.html#task-1-publish-and-protect-bluesky-app
Hello Kayjay88,
Thanks for posting to our community! I noticed that there was a good amount of information provided from members and wanted to see if there was an update you can provide or if you were needing additional assistance. If the answers you have received did get you the details needed, we would love to see the post marked as solved with what got you there. This will help you and others that may come across this in the future.
-Melissa
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
