Quick Sign-In lets the Egnyte Desktop App Core connect an organization-managed drive with minimal steps. When the app is deployed through an MDM (for example, Microsoft Intune) with SSO drives and Microsoft Entra ID settings in the configuration profile, it reuses the Entra ID session already present on the managed Mac to authenticate the drive.
Available starting in Desktop App Core v1.23.0 for Mac. This does not apply to the Desktop App for Mac (Legacy version) or to the Desktop App for Windows.
How It Works
Desktop App Core obtains a sign-in token from Microsoft Entra ID through the Microsoft Authentication Library (MSAL), using the Entra ID account that the user is already signed in with on the device. The app sends the token to Egnyte, which verifies that it was issued by the user’s Entra ID tenant, and then the drive connects.
Egnyte never sees the user’s password and does not store Entra ID credentials. If a token cannot be obtained, for example because the Entra ID keys are missing from the profile or there is no Entra ID session on the device, the app falls back to the standard browser-based SSO sign-in.
Prerequisites
- Egnyte domain: Admin access to change Settings > Configuration > Security & Authentication. SAML 2.0 SSO with Microsoft Entra ID must be configured on the domain (steps are included below if it is not yet set up).
- Microsoft Entra ID: A role that can create and configure enterprise applications, such as Cloud Application Administrator, Application Administrator, or Global Administrator. Ownership of the existing Egnyte application is also sufficient. Basic SAML SSO does not require an Entra ID Premium license.
- MDM: An MDM that can deploy macOS configuration profiles. Devices must be enrolled, and users must sign in to the Mac with their Microsoft Entra ID account so that an Entra ID session exists for Desktop App Core to reuse.
- Desktop App Core: v1.23.0 or later, deployed with a configuration profile. See Desktop App Core Configuration Profile Support for the base profile.
Part 1: Configure the Application in Microsoft Entra ID
If the Egnyte domain already uses SAML SSO with Entra ID, the existing enterprise application can be reused, and step 1 and 2 can be skipped. SSO Setup instructions are also available in this article.
Step 1: Create the Enterprise Application
- In the Microsoft Entra admin center, go to Applications > Enterprise applications > New application > Create your own application.
- Enter a name for the application (for example, Egnyte).
- Select Integrate any other application you don't find in the gallery (Non-gallery) and click Create.
Step 2: Collect the Application (Client) ID and Directory (Tenant) ID
- In the Entra admin center, go to App registrations > All applications and open the application that was created.
- On the Overview page, copy these two values. This will be needed for the MDM profile:
- Application (client) ID
-
Directory (tenant) ID
Step 3: Add the Redirect URI for Desktop App Core
- In the application, go to Manage > Authentication (Preview).
- Under Platform configurations, click Add a platform and select Mobile and desktop applications.
- Add the following custom redirect URI and click Configure:
msauth.com.egnyte.DesktopApp://auth - Scroll to Advanced settings and set Allow public client flows to Yes.
- Click Save.
If a redirect URI is already listed under the iOS/macOS platform, that value should be copied instead, because it must match the MSALRedirectUri value in the MDM profile exactly.
If the new Entra authentication experience is in use, these options may be in a different location. Switching to the previous experience can make them easier to find.
Step 4: Add API Permissions
- In the application, go to Manage > API permissions.
- Under Configured permissions, confirm the following Microsoft Graph delegated permissions are present: email, offline_access, openid, and profile.
- If any are missing, click Add a permission > Microsoft APIs > Microsoft Graph > Delegated permissions > OpenId permissions, select the missing permissions, and click Add permissions.
Step 5: Configure SAML Single Sign-on
Skip this step if SAML SSO between Entra ID and the Egnyte domain is already working.
- In Enterprise applications, open the application and go to Single sign-on > SAML.
- In Basic SAML Configuration, set:
- Identifier (Entity ID): https://saml-auth.egnyte.com
- Reply URL (Assertion Consumer Service URL): https://<yourdomain>.egnyte.com/samlconsumer — add one Reply URL for each Egnyte domain this application will serve.
- Leave Sign on URL, Relay State, and Logout URL empty.
- Click Save.
Step 6: Assign Users
- In the application, go to Users and groups > Add user/group.
- Assign every user or group who will sign in to Egnyte through this application.
Users must be assigned to the application or SSO will not work for them. An unassigned user can authenticate with Microsoft but is then rejected with error AADSTS50105.
Step 7: Download the Federation Metadata
- Go to Single sign-on > SAML Certificates.
- Next to Federation Metadata XML, click Download.
This file contains the login URL, entity ID, and signing certificate that Egnyte needs. It will be imported in Part 2.
Part 2: Configure SSO on the Egnyte domain
Skip this part if SAML SSO with Entra ID is already configured on the domain.
- In the Egnyte Web UI, go to Settings > Configuration > Security & Authentication.
- Under Single sign-on authentication, select SAML 2.0.
- For Identity provider, select AzureAD.
- Click Import metadata XML file and upload the file that was downloaded in Part 1, Step 7. This fills in the Identity provider login URL, entity ID, and certificate automatically.
- Set Default user mapping to Email address.
- Click Save.
Repeat these steps on every Egnyte domain served by the application.
Set Up Users for SSO
Each user must exist on both sides:
- In Entra ID, assigned to the enterprise application.
- In Egnyte, present on the domain with an email address (or IdP Username) matching the identity Entra ID being sent, and with Authentication type set to SSO.
When Egnyte receives a sign-in from Entra ID, it looks for an Egnyte user whose IdP Username or email that matches the identity.
Part 3: Add the Entra ID Keys to the MDM Configuration Profile
Quick Sign-In is turned on by three keys in the Desktop App Core configuration profile. Add them at the top level of the configuration, alongside the Drives array, and make sure each managed drive that should use it has UseSSO set to true.
<key>MSALTenantId</key>
<string>DIRECTORY_TENANT_ID</string>
<key>MSALClientId</key>
<string>APPLICATION_CLIENT_ID</string>
<key>MSALRedirectUri</key>
<string>msauth.com.egnyte.DesktopApp://auth</string>Replace DIRECTORY_TENANT_ID and APPLICATION_CLIENT_ID with the values that were copied in earlier. If the redirect URI differs from the default shown above, use the value registered in Part 1.
If an Egnyte Configuration Profile Is Already Deployed in Intune
- In the Microsoft Intune admin center, go to Devices > macOS > Configuration.
- Open the existing Egnyte configuration profile and go to Configuration settings > Edit.
- Copy the profile XML into a text editor, add the three keys above, and save the file.
- Upload the updated file, then click Review + save > Save.
If an Egnyte Configuration Profile Does Not Yet Exist
- Download the sample profile from Desktop App Core Configuration Profile Support, set the domain and drive settings, and add the three keys above.
- In Intune, go to Devices > macOS > Configuration > Create > New policy.
- Set Profile type to Templates, select Custom, and click Create.
- Enter a name and description, upload the XML file, assign the profile to the device group, and save.
Once the profile reaches the device, Desktop App Core needs to be restarted for the new settings to apply.
Parameters
Parameter |
Value |
Description |
| MSALTenantId | Entra ID Directory (tenant) ID (GUID) | Identifies the organization's Entra ID tenant. Use the specific tenant GUID, not common. |
| MSALClientId | Entra ID Application (client) ID (GUID) | Identifies the enterprise application configured for Egnyte in Part 1. |
| MSALRedirectUri | msauth.com.egnyte.DesktopApp://auth | The redirect URI registered under Mobile and desktop applications in Part 1, Step 3. Must match exactly. |
| UseSSO (per drive) | true or false | Existing drive setting. Must be true for a drive to use Quick Sign-In. Defaults to false. |
Miscellaneous Information
- The three MSAL keys are needed to enable this feature. To stop using Quick Sign-In, remove the keys from the profile. The drives will then return to the standard browser-based SSO sign-in. No data is lost. Users can restart their machines, to force a sync of the configuration profile
- If the token cannot be obtained or is rejected (for example, no Entra ID session on the device, the user is not assigned to the application, or the tenant does not match the one registered with Egnyte), the app falls back to browser SSO rather than showing an error.
- Conditional Access and device compliance policies in the Entra ID tenant are enforced before a token is issued to Desktop App Core, the same as for other applications.
- On the first sign-in, macOS may show a one-time consent dialog. The user must accept it to continue.
- After a reboot, the drive reconnects with its stored Egnyte session; no new sign-in is required.