SSO Configuration for Microsoft ADFS with Microsoft On-Prem Services and On-Prem Active Directory

Microsoft Active Directory Federation Services or ADFS is a Microsoft technology that enables single sign-on (SSO) to applications across different organizational boundaries. It allows users to authenticate once with their on-premises credentials to access various resources, both on-premises and in the cloud, by creating a trust relationship between systems and issuing security tokens.

Scalefusion’s OneIdP can be used to be configured as an IdP for Microsoft ADFS to add an extra layer of security where access to the applications can be made conditional with OneIdP’s conditional SSO and Extended Access Policies.

Pre-requisites

1. An existing setup of Microsoft ADFS configured as the claims provider for Microsoft 365 or Microsoft On-Prem applications.

2. A Scalefusion account with a valid subscription to OneIdP and access to SSO configuration section.

3. If using Microsoft ADFS for Microsoft 365 then an Entra Admin account that can grant the required permissions to Scalefusion OneIdP.

Step 1: Setup User management

Basing on your current IdP please configure the user management. You can choose to import the users from Microsoft Entra or configure Scalefusion On-Prem Connector.

Step 2: Configure a Directory and Migrate Users

The next step is to configure a OneIdP directory for your users by adding your domain and configuring the migration rules. Please refer to the Directory configuration guide.

Step 3: Create a Microsoft ADFS SSO Configuration

1. Sign in to Scalefusion Dashboard and navigate to OneIdP > SSO Configuration

2. Click on New SSO Configuration button on top right.
   

   

3. After clicking New SSO Configuration, a window will appear. Search for Microsoft ADFS in the list, select it, and then click Configure.
   

   

4. This opens the SSO Configuration wizard with following tabs on the left panel:

   1. Application Basics

   2. SSO Scope Management

   3. Permissions

   4. SSO Settings

   5. Conditional Access

   6. User Facing Messages
      Navigate to each tab and enter required details. You can navigate to next tab only after you have entered complete details in the current section. All are explained in detail below.

Application Basics

Configure basic application details by entering the following:

• Enter Application Name: Enter a name for your App which will be an identifier for your configuration. The name must be at-least 5 characters long. The maximum allowed length is 128 characters.

• Select Hosting Type: Select the option On-Premise.

• Configuration Type: Select the following:

  • Microsoft On-Prem Services with On-Prem AD: Customers who are using On-Prem suite of MS services and AD but use ADFS to allow users to sign in from corporate network or other IdPs

• Select Domains: All the custom domains you have configured and verified using OneIdP, will be listed here. Select the domain(s) which you want to be SAML SSO enabled.

• Select Authentication Type: This will be pre-selected as SAML.

• Enter Login URL: Provide URL that you use to sign in to that service.
  
  Once you have entered all details click Next
  

  

SSO Scope Management

With SSO scope management you can configure the procedure for managing the users who will be accessing this application. It basically allows how SAML settings for the users are going to be managed. Following are the settings:

Group-based SSO Profiles

User assignment

SSO Configuration would allow only assigned users to access the app. Choose one from the following options:

1. Allow all users imported to Scalefusion to access the application: All users (belonging to the domain) imported to Scalefusion and migrated to OneIdP will be allowed to access the application.

2. Allow only assigned users to access the application: Only the user(s) whom you have assigned the SSO configuration, will be allowed to access the application. With this option, after SSO configuration is created, you need to manually select and assign the users.

   1. Revoke access for all users once when the configuration is saved: If this is checked, the access is revoked from the users who are currently assigned with the configuration. As a result, it will invalidate all user sessions and logout users from their current running session.
      
      

Enforcement Rules

From here, you can configure and enforce users that at what point of time SSO Configuration should invalidate the current session and logout users. Following options can be selected:

1. Immediately on User Assignment and post grace period if applied: Once SSO configuration is assigned to user

2. Immediately on User Un-Assignment: When user is unassigned the SSO configuration

3. Immediately on Deleting this configuration: When SSO configuration is deleted from Scalefusion Dashboard

   Users will not get logged out in case of ADFS

   
   

   

Permissions

If the configuration type is Microsoft On-Prem Services with On-Prem AD, then you do not need to grant any additional permissions. Click Next to go to the next step.

SSO Settings

This section allows admins to configure the Service Provider (ADFS) settings and obtain the SSO URLs that will be added to the ADFS server.

OneIdP SSO Settings

Download the OneIdP Metadata by clicking on Download Metadata, from Scalefusion Dashboard (SSO Settings) and remember the location where it was downloaded to. This will be used to configure the ADFS.

Service Provider Settings

1. Service Provider Entity ID: If your service provider has given you an Entity ID, also known as an audience or identifier, please enter it here. Otherwise, leave it blank to have it automatically decoded from the incoming request.

2. Service Provider ACS URL: If your service provider has provided an ACS URL, sometimes also called a destination or recipient, then please enter it here, else leave it blank to auto-decode it from the incoming request

   The Entity ID and ACS URL should be set to the URL of your ADFS Login page which may be in the format of https://<adfs.your domain>/adfs/ls/idpinitiatedsignon.htm

Step 4: Create a Microsoft ADFS SSO Configuration

Conditional Access

From this section you can define the additional conditions on the basis of which users will be allowed/disallowed from accessing the application on device. This is divided into following sections:

1. Conditional Access Settings

2. Access Exceptions

Conditional Access Settings

Device Policy

1. For Android, iOS/iPad OS, Windows & macOS, Linux, Chrome OS: Choose one from the following two conditions:

   1. Only if the device is managed by Scalefusion: The application will be accessible only on devices managed (enrolled) by Scalefusion.
      

   2. If the device is managed by Scalefusion or an OTP using Scalefusion Authenticator app from a managed device: The application is accessible if any of the following conditions is met:

      1. Device is managed by Scalefusion: If device is managed you will not be asked to enter OTP for authentication, or

      2. If device is unmanaged, OTP is required for authentication. OTP can be taken from Authenticator app installed on a Scalefusion managed device.

   3. Allow users to access by setting up MFA using third party authenticator app or OTP sent on email: This option is activated only when Multi-factor Authentication is enabled in Directory Settings.
      Note: The left side panel is for configuring Device Policy on Android & iOS/iPad OS and right side is for Windows & macOS and Linux, ChromeOS below them. Hence, you can configure separate device policies based on platform.

   4. Skip Password on Scalefusion managed devices: When enabled, this option allows users to access applications on managed devices without the need to enter a password during sign-in.
      
      
      

Browser Policy

From here, you can select one or more browsers and specify minimum versions on which you want to allow the access to the application. Following are the options:

• All Browsers

• Google Chrome with minimum version

• Microsoft Edge with minimum version

• Safari with minimum version

• Mozilla Firefox with minimum version

Important Points on Browser Policy:

1. By default all browsers are allowed.

2. Only major versions are validated. For eg. if you mention browser version: 23.5.8.10 then the respective browser with minimum major version(23) will be allowed. After configuring Device Policy and Browser Policy, click Next
   

Access Exceptions

From this section you can configure the exceptions where the users are allowed to access the applications even if the conditions are not met. In general, these exceptions will be useful or addresses scenarios where :

1. IT Admins have setup Android Enterprise using Google Workspace Or

2. IT Admins have setup Apple User Enrollment with ABM/ASM federated to Google Workspace

Following are the exceptions that can be configured:

1. Enrollment Exceptions

   1. Allow users to access the application till they enroll their first device: Allows users to access the application till they enroll at-least one device. This option is helpful in conditions where the enrollment steps requires them to authenticate with the service provider. With this, you can also configure the following:

      1. Maximum sessions allowed per user: Configure no. of sessions that should be exempted. It can range from 1 to 3. Ideally 1 session per user is recommended.

      2. Configure the OS where the exceptions are applied: Select the platform(s) on which this exemption would be allowed to users.

2. User Exceptions
   Here you can add the users who are always exempted from the conditions and will never be asked to manage their device. Enter comma separated email addresses of users or click on Add Users on the right and in the new window, select the users who should be exempted.
   Note: These users still need to sign in with their OneDirectory credentials if they fall under the SSO Scope, however the conditions will not be enforced.
   
   

User Facing Messages

User Facing Messages helps admins configure messages that end users may be shown when they are unable to access the application if any of the compliance conditions are not met. You can configure messages under following:

• Configure Instructions for a Non-Compliant Device: This message is shown when the device is not compliant and needs to be enrolled to Scalefusion

• Configure Instructions for a Non-Compliant Browser: Shown when the browser is not compliant as per configurations

• Configure a Message to be displayed when Access is Denied: Any other cases where access to application is denied.

There are some pre-configured messages displayed on Dashboard which you can edit as per requirement.

After configuring user facing messages, click on Save

The SSO configuration is created and listed on SSO Configuration page as a separate card with the name you have defined. You can create multiple SSO configurations in the same manner.

Steps to configure OneIdP as Claims Provider Trust

1. Locate the metadata file downloaded in Step 3 above (SSO Settings > Service Provider Settings)

2. Login to the Windows sever machine where you have the Microsoft ADFS setup.

3. On your ADFS server machine, launch Server Manager -> AD FS Management. Click on “Claims Provider Trusts” and select “Add Claims Provider Trust”
   

   

4. In the “Add Claims Provider Trust Wizard”, under “Select Data Source”, choose the 2nd option: “Import Data about the claims provider from a file”. Click on Browse and select the metadata file downloaded from Scalefusion Dashboard (Step #3). Click Next.

   

5. Provide an appropriate display Name (Eg: OneIdP) and give Notes. Click Next.
   Note: This display name will be shown in your ADFS login page.

   

6. In “Ready to Add Trust” do not change anything. Click on Next. In the last window, Ensure that “Open the Edit Claim Rules dialog for this claims provider trust when the wizard closes” is checked and click on Close.

   

7. In the “Edit Claim Rules for OneIdP” window, click on “Add Rule”, Select “Pass Through or Filter an Incoming Claim”. Click Next.

   1. Set the Claim Rule name as “Pass Through all Windows account name”.

   2. Select the Incoming claim type as “Windows account name” from the drop down.

   3. Ensure that the radio button “Pass through all claim values” is selected.

   4. Click Finish, Click Yes.

      

8. Repeat step 6 for the following Incoming Claim types:

• Name

• Primary SID

• Enhanced Key Usage

• UPN

After adding these rules, your “Edit Claim Rules for OneIdP” window should look like this:

Click Apply and OK to save.

Add ECP in Relying Party Trusts

9. Next, go to AD FS Management. Click on “Relying Party Trusts” and select “Add Relying Party Trust”
   

   

10. This will open the Add Relying Party Trust Wizard. Click on Start
    

    

11. In the next window, leave the default option as selected and click Next
    

    

12. Provide an appropriate display Name (Eg: ECP) and give Notes. Click Next.

    Note: This display name will be shown in your ADFS login page.
    

    

13. In the Configure Certificate, click Next
    

    

14. Configure URL: Enter the URL under the first option and click Next
    

    

15. Configure Identifiers: The URL you have entered will be auto-populated. Click Next
    

    

16. Choose Access Control Policy: Click Next
    

    

17. Ready to Add Trust: Click Next
    

    

18. Finish: Click Close
    

    

19. This will display ECP (or the name you have specified) under Relying Party Trusts. Select it and click on Edit Claim Issuance Policy on the right section.
    

    

20. In the Add Transform Claim Rule Wizard, click on “Add Rule”, Select “Pass Through or Filter an Incoming Claim”. Click Next.

21. In the Configure Claim Rule, click Finish
    

    

22. The rule will be listed. Click Ok
    

    

Add OWA in Relying Party Trusts

Add OWA as Relying Party Trusts. To do so, follow the steps #9 through #22 above (same as ECP above).

Now, navigate back to Scalefusion Dashboard and click Next to configure rest of the settings.

Step 5: Checking the Integration

To test the configuration, open https://<adfs.your domain>/adfs/ls/idpinitiatedsignon.htm on any machine connected to the domain.

You should be able to see OneIdP as one of the sign-in options, clicking on which will redirect you to OneIdP login page. Enter your user oneIdP credentials to verify if the login is working.

Step 6: Integration with OWA (Outlook Web App)

1. Enroll a device and access Outlook in chrome browser.
   

   

2. When trying to login to Outlook the you will be presented with the options to Sign in with OneIdP and the Active Directory. Select OneIdP.
   

   

3. Enter your credentials and follow steps to check compliance and complete the sign in.
   

   

   
   
   

4. You should be signed in to your account after compliance check.