Hello,
I have a request from customer to set up SSO via SAML + Kerberos Constrained Delegation. SAML is working but I have problem with the kerberos delegation. The backend server is IIS on Windows 2016 server.
I set everything I found in the admin guide for Fortiweb - KDC server, the SPN's, the account and delegation, application pool in IIS and changed on IIS the useAppPoolCredentials to True + use the service account.
However it seems to me that the fortiweb does not communicate with the KDC. There is no packet sent to KDC to obtain a kerberos ticket on behalf of the user.
Does anyone have an idea where the problem should be? Or maybe a bug?
Fortiweb VM is used with firmware version: FortiWeb-VM 6.01,build0036,180822
AtiT
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
What I found in getting Kerberos to work in FortiWeb is making sure the "Delegated HTTP Service Principal Name" is absolutely correct with case sensitivity. The domain portion should be in upper case.
I think FortiWeb itself passes the packets to IIS so the KDC communication is still from IIS.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1720 | |
1093 | |
752 | |
447 | |
234 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.