SWIFT REALM BROWSER FOR DEVICE SOFTWARE
SWIFT REALM BROWSER FOR DEVICE MAC
SWIFT REALM BROWSER FOR DEVICE WINDOWS

MDM deployment of SSO extension configuration profile When the Terminal opens type sw_vers at the prompt, look for a result like the following: % sw_vers The Operating system version will be listed beside macOS.įrom the macOS device, open Terminal from the Applications -> Utilities folder. User interfaceįrom the macOS device, click on the Apple icon in the top left corner and select About This Mac. You can check the macOS version from either the User Interface or from the Terminal. Apple SSO Extension profiles will only be deployed to devices running macOS 10.15 (Catalina) or greater. Use the following steps to check the operating system (OS) version on the macOS device.

SWIFT REALM BROWSER FOR DEVICE SOFTWARE

Authentication Broker Software installed: Microsoft Intune Company Portal or Microsoft Authenticator for iOS.

Device is managed by any MDM vendor that supports Apple macOS and/or iOS (MDM Enrollment).

iOS operating system: version 13 or greater.

macOS operating system: version 10.15 (Catalina) or greater.

SWIFT REALM BROWSER FOR DEVICE MAC

This section will cover the steps you can take to ensure that the MDM profile has been deployed to a Mac and that it has the correct configuration. Most issues that customers encounter stem from either improper Mobile Device Management (MDM) configuration(s) of the SSO extension profile, or an inability for the Apple device to receive the configuration profile from the MDM. The troubleshooting can be broken down into two separate focus areas: Deployment and Application Auth Flow. The rest of this article will go into detail on the steps depicted in this flowchart. The following flowchart outlines a logical flow for approaching troubleshooting the SSO Extension. For more information, see the article What is a Primary Refresh Token.

SWIFT REALM BROWSER FOR DEVICE WINDOWS

When deployed through an MDM, the Enterprise SSO extension for macOS or iOS obtains a PRT that is similar to the PRTs used on Windows devices by the Web Account Manager (WAM). Microsoft Intune Company Portal (via SSO Extension)Īll Microsoft broker applications use a key artifact known as a Primary Refresh Token (PRT), which is a JSON Web Token (JWT) used to acquire access tokens for applications and web resources secured with Azure AD. Microsoft Authenticator or Microsoft Intune Company Portal Microsoft has implementations for brokered authentication for the following client operating systems: OS Request data then get challenged for authentication. If handled, the extension returns the authorization headers to complete the request, and authentication server will return response to the caller.

The extension has the choice of handling or rejecting the challenge. If the authentication server returns a challenge that matches a host listed in the profile, the operating system will route the challenge to the extension. Credential extensions are configured with HOSTS in the MDM configuration profile. Request is sent from the application to the authentication server (AD domain controller). Uses URLs in MDM configuration profile.Ĭhallenge and response authentication types like Kerberos (on-premises Active Directory Domain Services) Request credentials before requesting data. Redirect extensions receive: URLs, headers, and body. Operating System intercepts the authentication request from the application to the Identity provider URLs defined in the extension MDM configuration profile. Modern authentication methods such as OpenID Connect, OAUTH2, and SAML (Azure Active Directory) The following table compares the two types of extensions. The Microsoft Enterprise SSO plugin has been implemented as a Redirect type and is best suited for brokering authentication to Azure AD. Extension typesĪpple supports two types of SSO Extensions that are part of its framework: Redirect and Credential. For more information, see the article Microsoft Enterprise SSO plug-in for Apple devices.

Microsoft has implemented a plugin built on top of Apple's SSO framework, which provides brokered authentication for applications integrated with Microsoft Entra Azure Active Directory (Azure AD). SSO relieves end users of the burden of excessive authentication prompts. On Apple platforms, this process involves implementing Single Sign On (SSO) via Primary Refresh Tokens. Organizations may opt to deploy SSO to their corporate devices to provide a better experience for their end users. The Apple SSO extension can be deployed to iOS/iPadOS and macOS. This article provides troubleshooting guidance used by administrators to resolve issues with deploying and using the Enterprise SSO plugin.

Swift realm browser for device