Extensible Single Sign-On and Active Directory

Current mode: Dark

Introduction

This is part two of a six part blog series on how to configure Apple Platform SSO using Omnissa Workspace ONE Unified Endpoint Management (UEM). Each part of the blog covers the various vendor configuration options and the series wraps up with a blog dedicated to troubleshooting. As each vendor continues to change their implementation these blogs will be updated.

Part 1 – What is Apple Platform SSO

Part 2 – How to configure Apple Platform SSO for Kerberos with Microsoft AD or Microsoft Entra

Part 3 – How to configure Apple Platform SSO with Microsoft EntraID

Part 4 – How to configure Apple Platform SSO with Okta Desktop Password Sync

Part 5 – How to configure Apple Platform SSO with Omnissa Access

Part 6 – Troubleshooting

Microsoft and Apple have a long history of developing frameworks to allow macOS to interact with Microsoft Active Directory. Over time the tools and methods have evolved and many organizations pay for 3rd party tools to address gaps in the Apple developed frameworks. Microsoft summed up this history in one of their presentations using the following slide:

Apple Inc tends to present this topic using a similar slide:

The point of both of these illustrations is that as Apple continues to move the macOS login into the future, there are now fewer and fewer reasons to bind macOS to Active Directory.

The rest of the blogs in this series speak to customers that are truly leaving AD behind (or never had it to begin with) and need macOS to authenticate against a directory that is NOT AD. But what if you plan to keep AD? Or what if you are going to stay in Hybrid AD for as long as Microsoft lets you? This means you need to configure macOS to continue to use Kerberos without binding to AD. And that is the purpose of configuring the Apple MDM payload Extensible Single Sign-On payload (com.apple.extensiblesso).

The first decision point to make is where does Kerberos live. If you only have AD, use Option 1. Hybrid Customers should stick with Option 1. If someone convinced you to move Kerberos to EntraID, Option 2 exists, but well…. good luck with that.

Option 1: PSSO Kerberos with Microsoft Active Directory (AD)

In the Workspace ONE UEM Console add a new Profile > Apple macOS > Management Type Imperative, Context Device > Choose SSO Extension and configure the following:

NameSettingNotes
Extension TypeKerberos
RealmLAB.AFTERSIXCOMPUTERS.COMThis is the Fully Qualified Domain Name (FQDN) of the AD Forest.

It is CASE SENSITIVE. MUST BE ALL CAPS.

Use as default realmEnable
Domainslab.aftersixcomputers.com
testing.lab.aftersixcomputers.com
Use Site Auto-DiscoveryEnable
Allow Automatic LoginEnable
Use Platform SSO TGTEnable
Allow Authentication FallbackEnable
Perform Kerberos onlyNOT ENABLED
Identity Issuer Auto Select FilterLeave Blank
Allow SmartCardNOT ENABLED
Allow PasswordEnable
Start in Smart Card ModeNOT ENABLED
Require Biometric AuthenticationEnabled
Delay User SetupChoose NOT Configured
Credential use modeAlways
Monitor Credential cacheEnable
Require TLSEnable
Principal Name{UserPrincipalName}
Custom Username LabelLeave Blank
Help TextType what you wantNever seen this text displayed so not sure where it shows up on the device
Site CodeLeave Blank
CertificateNone
Allowed Bundle IDscom.apple.Safari
com.google.Chrome
com.apple.Terminal
com.apple.dt.Xcode
Prefered KDCsLeave Blank
Allow Kerberose to use credentialEnable
Require Managed ApplicationsChoose NOT Configured
Allow Password ChangeEnable
Sync Local PasswordEnable
Match AD Password ComplexityEnable
Password Change MessageAfter Six Computers IT Department requires you to change your password. Thank you for your assistance in keeping our systems secure.Adjust to your company liking
pwReqRTFDataLeave Blank
Minimum Password Length (in characters)4
Password History Count (number of passwords)0
Password Minimum Age (in days)0
Password Expire Notification (in days)365
Password change URLLeave Blank
Custom XMLLeave Blank

A few important details about the configuration above:

What none of the vendors documentation agrees on is the format for the <key>Hosts</key>. You need to adjust this to match the AD domains in your environment. In my environment for example, in theory, *.lab.aftersixcomputers.com is supposed to be the same as .lab.aftersixcomputers.com but in testing attempts to use the * would never allow the device to retrieve the TGT. I found that if I use a period in front of the Hosts name instead of an asterisk this seems to work.

Kerberos Realm selection can be confusing. Apple macOS selects the default Kerberos realm based on the first SSO extension that establishes an authenticated identity during login. For organizations leveraging Microsoft 365 the recommendation here is to let Apple macOS pick the default Kerberos realm based which is achieved by NOT using <key>isDefaultRealm</key><true/>. This key has been left out of the configuration above on purpose in order to allow macOS to choose the correct realm.

For Microsoft 365 customers, it will be often be necessary to deploy a second SSO Extension Payload, detailed in Part 3 of this blog series. When using two SSO Extension payloads on the same device, Apple supports a key named isDefaultRealm or it can be left out of the payload entirely which is the recommended approach.

Option 2: PSSO with Microsoft EntraID Kerberos

This configuration is only used when Microsoft Active Directory does not exist and there is a Kerberos resource in Microsoft EntraID that needs to be used.

I have not found anyone in this state so the following is more theory than actual recommendation but I did test this and it deployed.

If this is your configuration reach out so we can community source a working config for this. The approach below was tested and confirmed to install successfully, it was just not fully vetted beyond “did it install.”

NameSet Value To
Extension TypeKerberos
RealmAFTERSIX.ONMICROSOFT.COM
Use as default realmNot Configured
Domainsaftersixcomputers.com
windows.net
.windows.net
KERBEROS.MICROSOFTONLINE.COM
MICROSOFTONLINE.COM
.MICROSOFTONLINE.COM
Use Site Auto-DiscoveryEnable
Allow Automatic LoginEnable
Use Platform SSO TGTEnable
Allow Authentication FallbackEnable
Perform Kerberos OnlyDisable
Identity Issuer Auto Select FilterLeave Blank
Allow SmartCardDisabled
Allow PasswordEnable
Start In Smart Card ModeDisable
Require Biometric AuthenticationNot Configured
Delay User SetupDisable or Not Configured
Credential Use ModeAlways
Monitor Credential CacheEnable
Require TLSNot Configured
Principal Name{UserPrincipalName}
Custom Username LabelLeave Blank
Help TextLeave Blank
Site CodeLeave Blank
CertificateNone
Allowed Bundle IDsLeave Blank
Preferred KDCskkdcp://login.microsoftonline.com/aftersix.onmicrosoft.com/kerberos
Allow Kerberos to use credentailEnable
Require Managed ApplicationsNot Configured
Allow Password ChangeEnable
Sync Local PasswordEnable
Match AD Password ComplexityEnable
Password Change MessageYour choice
pwReqRTFDataLeave Blank
Minimum Password Length (in characters)4
Password History Count (number of passwords)0
Password Minium Age (in days)0
Password Expiration Notification (in Days)365
Password Change URLLeave Blank
Additional Settings > Custom XMLLeave Blank

A few important details about the configuration above:

Realm: To find the correct value for your environment login to https://entra.microsoft.com select the Identity Blade and select Overview. The primary domain is listed there.

Domains: You’ll notice that I am using aftersixcomputers.com not .aftersixcomputers.com (missing the leading wildcard period) and for that matter not aftersix.onmicrosoft.com. This is because in my environment lab.aftersixcomputers.com is the name of the AD Forest. aftersixcomputers.com is an EntraID Custom domain name. I am making sure that macOS understands the distinction by leaving off the wildcard entry for the domain.

Another oddity is that I do not understand why windows.net is not capitalized, but the other Microsoft sites are. I tried changing these and well, don’t do it. It just breaks everything. So make sure you are following this otherwise odd capitalization for all the Microsoft domain names.

Principal Name. Notice that I’ve left this at the default because in my environment UPN is the email address which is the format EntraID is expecting.

Preferred KDCs. Notice the format is different than the other payload. For AD it’s kerberos:// but for EntraID it’s kkdcp://. Make sure you change the domain to your own primary EntraID domain.

Next Steps

Now that you’ve configured SSO for Kerberos, ff you are also using Microsoft Entra the next step is to configure PSSO with EntraID. Part 3 covers how to add a second profile to UEM for Microsoft Entra ID which would focus on apps like Microsoft 365. Otherwise checkout Part 6 for Troubleshooting.

Part 1 – What is Apple Platform SSO

Part 2 – How to configure Apple Platform SSO for Kerberos with Microsoft AD or Microsoft Entra

Part 3 – How to configure Apple Platform SSO with Microsoft EntraID

Part 4 – How to configure Apple Platform SSO with Okta Desktop Password Sync

Part 5 – How to configure Apple Platform SSO with Omnissa Access

Part 6 – Troubleshooting