Enable automatic authentication for iOS and macOS devices using a single sign-on extension profile

Single sign-on extension profiles are supported for iOS and macOS devices with the MDM controls activation type, and for iOS devices that use the User privacy activation type with management of all profiles enabled. If you configure more than one single sign-on extension profile for Platform SSO for macOS devices, only one profile should be assigned to macOS devices at a time; if a macOS device receives Platform SSO configurations from multiple profiles, it will report an invalid configuration error to UEM and will not apply the profiles.
  • If you want to use certificate-based authentication, you must first create a shared certificate profile, SCEP profile, or user credential profile.
  • If you want to configure the profile to use Platform SSO for macOS devices, and you want to use an access key as the authentication method for new users, you must first create a shared certificate or SCEP profile for the terminal identity, and a CA certificate profile for the issuer. For the CA certificate profile, the certificate must use an ECC key (devices reject certificates with an RSA key).
  1. In the management console, on the menu bar, click Policies and profiles > Networks and connections > Single sign-on extension.
  2. Click Add icon..
  3. Type a name and description for the profile.
  4. Select the device types that you want to configure the profile for.
  5. Click the tab for the OS that you want to configure the profile for (iOS or macOS).
  6. In the Single sign-on extension type drop-down list, click Custom extension, Kerberos built-in extension (iOS only), or Platform SSO (macOS only).
  7. If you selected Custom extension, do the following:
    1. In the Extension identifier field, type the bundle identifier of the app extension that performs SSO.
    2. If you are configuring the profile for macOS, in the Team identifier field, specify the Apple Developer team identifier of the SSO extension.
    3. Select the appropriate sign-on type.
    4. If you selected Credential as the sign-on type, do the following:
      1. In the Realm name field, type the realm name for credential payloads.
      2. In the Hosts section, click Add icon..
      3. In the Name field, type the host or domain for which the app extension performs SSO.
      4. Add additional hosts or domains as required.
    5. If you selected Redirect as the sign-on type, do the following:
      1. In the URLs section, click The Add icon.
      2. In the Name field, type the URL prefix for the identity provider for which the app extension performs SSO.
      3. Add additional URLs as required.
    6. If you are configuring the profile for macOS, in the Screen locked behavior drop-down list, select how you want devices to handle authentication requests when the screen is locked.
    7. In the Extension data field, enter the custom payload code for the app extension. To see a sample payload, click Payload format.
    8. If you are configuring the profile for macOS and you want to exempt specific apps from the SSO extension profile configuration, in the Denied bundle identifiers section, click The Add icon and type the bundle identifier of the app. Add additional bundle identifiers as required.
  8. If you selected Kerberos built-in extension for iOS, do the following:
    1. In the Hosts section, click Add icon.. In the Name field, type the host or domain for which the app extension performs SSO. Add additional hosts or domains as required.
    2. In the Realm name field, type the realm name for the Kerberos built-in extension.
    3. In the Apple Kerberos SSO extension data section, turn on the appropriate settings for your organization's environment. By default, automatic login and Active Directory autodiscovery are turned on.
    4. In the Principal name field, type the principal name for the connection.
    5. If you want to use a certificate profile to provide the PKINIT certificate for authentication, in the Select the PKINIT certificate for authentication drop-down list, select the appropriate profile type, then select the appropriate profile.
    6. If you're using the Generic Security Service API, in the GSS name of the Kerberos cache field, type the GSS name of the Kerberos cache.
    7. In the App bundle identifiers section, click The Add icon to specify the bundle IDs that are allowed to access the ticket-granting ticket.
    8. In the Preferred key distribution centers section, click The Add icon to specify preferred servers if they are not discoverable using DNS. Specify each server in the same format used in a krb5.conf file. The specified servers are used for connectivity checks and tried first for Kerberos traffic. If the servers do not respond, the device uses DNS discovery.
    9. In the Custom domain-realm mapping field, specify any required custom mapping of domains to realm names in payload format, for example <key>sample-realm1</key><array><string>org</string></array>.
    10. In the Login hint field, type the text to display at bottom of the Kerberos login window.
  9. If you selected Platform SSO for macOS, do the following:
    1. In the Extension identifier field, type the bundle identifier of the app extension that performs SSO.
    2. In the Team identifier field, specify the Apple Developer team identifier of the SSO extension.
    3. In the URLs section, click The Add icon. In the Name field, type the URL prefix for the identity provider for which the app extension performs SSO. Add additional URLs as required.
    4. In the Screen locked behavior drop-down list, select how you want devices to handle authentication requests when the screen is locked.
    5. In the Extension data field, specify the custom payload code for the app extension. To see a sample payload, click Payload format.
    6. If you want to exempt specific apps from the SSO extension profile configuration, in the Denied bundle identifiers section, click The Add icon and type the bundle identifier of the app. Add additional bundle identifiers as required.
    7. In the Authentication method drop-down list, click the appropriate Platform SSO authentication method.
      The OpenID authentication method applies only to devices with macOS 27 and later.
    8. In the Registration token field, type the token that devices use for silent registration with the identity provider.
    9. In the Account display name field, type the display name for the account in notifications and authentication requests.
    10. If you want to use the same signing and encryption keys for all users, select the If check box.
    11. In the Account name claim field, type the identity token claim to use for the local account name when creating or authorizing users.
    12. In the Full name claim field, type the identity token claim to use for the user's full name when creating users or authorizing users.
    13. In the Login frequency field, type the number of seconds before the device user must perform a full login. The minimum value is 3600 seconds (1 hour). If you don't specify a value, the default is 64,800 seconds (18 hours).
    14. If you want to allow users to be created at the login window, select the Enable create user at login check box. This setting is available only if you selected Use shared device keys and you set the Authentication method to Password or Smart card.
    15. By default, devices with macOS 26 or later use Platform SSO to create the first user account during the setup assistant. If you want to turn off this feature, clear the Enable create first user during setup check box.
    16. In the New user authentication methods section, select the authentication methods to use for new user accounts that are created at login or when the setup assistant is used. If you don't select any methods, Password and Smart card are used by default. Password, Smart card, and Access key apply to devices with macOS 26 or later. OpenID applies to devices with macOS 27 or later.
      If you select Access key, do the following:
      1. In the Access key reader group identifier field, type the reader group identifier configured for the access key.
      2. In the Access key terminal identity drop-down list, click Shared certificate or SCEP and then click the appropriate profile.
      3. In the Assign CA certificate profile drop-down list, click the appropriate CA certificate profile for the issuer of the terminal identity. This setting applies only to devices with macOS 26.2 or later.
      4. If you want the device to use the access key in express mode so that it does not require authentication before use, select the Allow access key express mode check box.
    17. In the New user authorization mode drop-down list, select the appropriate level of permissions to apply to user accounts that are created at login.
    18. If you turned on Use shared device keys and you want to allow identity provider accounts to be used at authorization prompts, select the Enable authorization check box.
    19. In the User authorization mode drop-down list, select the appropriate level of permissions to apply to a user account whenever the user authenticates successfully.
    20. If you set the New user authorization mode or User authorization mode to Groups, do the following:
      1. In the Administrator groups section, click The Add icon. Type the name of the group to use for administrator access. The device requests membership during the authentication process. Add additional groups as required.
      2. In the Additional groups section, click The Add icon. Type the name of a group that does not have administrator access. Add additional groups as required.
      3. In the Authorization groups section, click The Add icon. Type an authorization right and the name of the group that it is associated with. Add additional authorization right and group pairings as required.
    21. If you set the Authentication method to Password, Secure Enclave key, or OpenID, in the Policies section, select the policy rules that you want to turn on. See the tooltip for each rules section for details about the policy rules.
    22. If you set the Authentication method to Password, Secure Enclave key, or OpenID, and you want to exempt local accounts from the Platform SSO configuration, in the Non-Platform SSO accounts section, click The Add icon. Type the username of a local account that is exempt from the Platform SSO configuration. Add additional local accounts as required.
    23. If you set the Authentication method to OpenID, or you selected OpenID under New user authentication methods, in the Web login URL allow list section, click The Add icon. Type the host or host prefix that the device can load in the Platform SSO web view. Add additional hosts as required.
    24. If you want the device to include the device UDID and serial number in Platform SSO attestations, select the Allow device identifiers in attestation check box.
    25. If you want to request the user's profile picture from the SSO extension, select the Synchronize profile picture check box. This setting applies only to devices with macOS 26 or later.
    26. If you want to turn on authenticated guest mode login, select the Temporary session quick login check box. The device deletes user data from select locations in the user home directory after each session, and erases the full user home directory every 8 hours. This setting applies only to devices with macOS 26 or later.
    27. If you want to enable the Platform SSO registration process during the setup assistant, select the Enable registration during setup check box. This setting applies only to devices with macOS 26 or later.
    28. If you want the device to detect the user's password during web login and synchronize it to the local account password, select the Allow web login password sync check box. This setting applies only to devices with macOS 27 or later.
  10. Click Save.
Assign the profile to user accounts and groups. If you configure more than one single sign-on extension profile for Platform SSO for macOS devices, only one profile should be assigned to macOS devices at a time; if a macOS device receives Platform SSO configurations from multiple profiles, it will report an invalid configuration error to UEM and will not apply the profiles.