Kerberos authentication using the iOS Kerberos extension

Last published : Sep 24, 2026
This topic outlines the end-to-end configuration required to enable Kerberos-based Single Sign-On (SSO) for internal web apps via the Citrix Secure Access for iOS app.
  • iOS client configuration
  • MDM server configuration
  • IIS configuration
  • Domain controller configuration
Related information

iOS client configuration

Prerequisites

Ensure that the iOS device is MDM enrolled. The iOS device must be enrolled in an MDM solution (for example, Microsoft Intune) before any SSO configuration can be applied. MDM enrollment allows the Kerberos SSO extension profile to be pushed to the device.

Validate MDM enrollment on the iOS device

  1. On the iOS device, go to Settings > General > VPN & Device Management.
    Under Device Management, you must see your organization's MDM profile listed (for example, Microsoft Intune or your company's MDM profile name).
  2. Tap the profile to confirm it is installed and the status displays Verified or Installed.
  3. To confirm the Kerberos SSO extension was pushed by MDM:
    • Go to Settings > General > VPN & Device Management.
    • Tap the MDM profile, look for Single Sign-On Extensions or Kerberos under the profile details.
    • Alternatively, go to Settings > General > VPN & Device Management > Single Sign-On and verify that the Kerberos extension is listed.
    If the device is not enrolled or the profile is missing, contact your MDM administrator to enroll the device before proceeding.

MDM server configuration

Note:
The MDM SSO extension payload configuration is based on the official Apple documentation.
Ensure that the following fields are configured in the MDM SSO extension payload:
  1. Domain: The URLs that are used for Kerberos.
  2. AppBundleIDs: Allow list of apps that will be used. (For example, Chrome: com.google.chrome.ios, Citrix Secure Access: com.citrix.securehub)
  3. Realm: Location of your data center.

Intune policy configuration

Prerequisites: Ensure that the iOS device is enrolled into Intune.
  1. In the Intune Admin console, go to Home > Devices | iOS/iPadOS → iOS/iPadOS | Configuration.
  2. Create a new policy.
  3. In Profile type select Templates, and then select Device Features.
    Intune policy profile
  4. Press Create.
  5. Enter a name for the policy and then proceed to Configuration Settings.
  6. In the Single sign-on app extension > SSO app extension type select Kerberos.
    Intune policy SSO extension
  7. Fill in the information according to your setup requirements.
    Intune policy device features1Intune policy device features2
  8. Press Review + save.
  9. Bind the policy to your device:
    • Go to Edit Policy, click the policy.
    • Edit Assignments.
    • Select your Device Group (create a Device group with your device first if not yet created).
  10. Synchronize the device.

IIS configuration

On the IIS web server, enable Windows Authentication with the Negotiate provider and disable Anonymous Authentication to enforce Kerberos-based authentication.
Steps to configure IIS authentication:
  1. Open IIS Manager (inetmgr from Run or Start).
  2. In the Connections pane, select the site or application to configure.
  3. Double-click Authentication in the IIS section of the Features View.
  4. Disable Anonymous Authentication.
    • Select Anonymous Authentication, click Disable in the Actions pane.
  5. Enable Windows Authentication.
    • Select Windows Authentication, click Enable in the Actions pane.
  6. Set the Negotiate provider.
    • With Windows Authentication selected, click Providers… in the Actions pane.
    • Ensure Negotiate is listed first (above NTLM). Add it if missing.
    • Click OK.
  7. Click Apply in the Actions pane to save the changes.
  8. Optionally, run iisreset from an elevated command prompt to apply the configuration immediately.
    IIS authentication configuration

Domain controller configuration

SPN registration for short name and FQDN: Kerberos requires an exact match between the URL that the client uses and a registered SPN on the domain. A client accessing http://testwebdemo uses a different SPN than one accessing http://testwebdemo.example.com, so both must be registered.
  1. Replace <dc-hostname> below with the host name of your Domain Controller.
  2. Register both forms.
    • Short host name (used when client accesses via short name, for example http://testwebdemo)
      setspn -s HTTP/testwebdemo example.com\<dc-hostname>
    • FQDN (used when client accesses via full domain name, for example http://testwebdemo.example.com)
      setspn -s HTTP/testwebdemo.example.com example.com\<dc-hostname>
  3. Verify both are registered on the correct account
    • setspn -L example.com\&lt;dc-hostname>
  4. Expected output must include both:
    • HTTP/testwebdemo
    • HTTP/testwebdemo.example.com