SSO Configurations for any SAML app
  • 08 Jul 2024
  • 8 Minutes to read
  • PDF

SSO Configurations for any SAML app

  • PDF

Article summary

The first step is to create SSO Configuration in Scalefusion. This document provides a step-by-step guide for setting up SSO Configuration to configure any SAML application once authenticated by Scalefusion (Identity Provider) via SSO Configuration


  1. The devices should be enrolled with Scalefusion as BYOD or UAE or Shared COD.
  2. The Custom Domain for which you are authorizing, should be verified through OneIdP. 
  3. Users belonging to custom domain should be imported/added to Scalefusion Dashboard and migrated to OneIdP.
  4. IT Admins should have access to Service Providers' admin console.


  1. Sign in to Scalefusion Dashboard and navigate to OneIdP > SSO Configuration 
  2. Click on New SSO Configuration button on top right.
  3. 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:

  • Select Application Type: Select application type from the drop-down. If it's any other web-app supporting SAML choose Any other SAML app
  • 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 one from the following as hosting type:
    • Cloud (default)
    • On-Premise
  • 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. You can create multiple SSO configurations with same domains.
  • 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:

Select User Scope

Select one from the following options basing on how you intend to use the SAML settings. It is recommended to create a group in your application and applying these settings to only a group of users. Select one from the following:

  1. Groups based on Users (or subset) Imported to Scalefusion (Default)
  2. We will apply settings to All Users (Not Recommended)

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 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 you can configure and enforce users that at what point of time SSO Configuration should invalidate the current session and logout users (only for Google Workspace). Following options can be selected:

These rules can be applied only on Google Workspace users

  1. Immediately on User Assignment and post grace period if applied: When grace period is applied and user gets automatically added in the group on the admin console.
  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

Click Next


For any other SAML app, you do not need to provide additional permissions. Click Next to proceed to next step

SSO Settings

This section allows admins to configure the Service Provider settings and obtain the SSO URLs which will be added to the Service Provider's admin console.

  1. Enter the Service Provider details on Scalefusion Dashboard, as provided in the web-console of your service provider SSO/SAML section
    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
    3. SAML Subject Name Id Format: Most service providers accept Email as the SAML Subject NameID as the user identifier. Change this only if your service provider wants a different value. Select E-mail or username from the drop-down. 
    4. Session Duration: Configure the duration (in days) after which the user will be asked to re-authorize. Make sure to select a value potentially higher than your Service providers' session value. It can be anywhere from 5 to 90 days.
  2. OneIdP Entity ID: It is the Entity ID of Identity Provider (Scalefusion in this case). Copy this URL from Scalefusion Dashboard and paste it as the Entity ID of the Identity provider on the Service Provider's admin console. To be entered when you add a new SAML profile on the admin console and assign it to groups or organizational units. 
  3. OneIdP SSO URL: Copy this URL from Scalefusion Dashboard and paste it under the Sign-In page URL on Service Provider's admin console 
  4. OneIdP SLO URL: Copy this URL from Scalefusion Dashboard and paste it under the Sign-Out page URL on Service Provider's admin console 
  5. OneIdP Change Password URL: Copy this URL from Scalefusion Dashboard and paste it under the Change Password URL on Service Provider's admin console
  6. OneIdP Verification certificate: This certificate is used to sign the response to your service provider. Download the certificate by clicking on the download icon on Scalefusion Dashboard. This certificate has to be uploaded at the time of adding a new SAML SSO profile on the admin console.

Click Next

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: 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 OneIdP 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.
        Note: The left side panel is for configuring Device Policy on Android & iOS/iPad OS and right side is for Windows & macOS. Hence, you can configure separate device policies based on platform.
  2. For Linux: Admins can configure rule for Linux devices to either not allow access on Linux device or allowing it via the OTP method with the following setting:
    Always allow access on Linux/Ubuntu devices: Enabling this will allow access on Linux/Ubuntu devices without user having to enter an OTP. Disabling this will enforce OTP based access on Linux/Ubuntu devices, which the user can obtain by enrolling their Android or iOS device. Users will always be enforced to enter a password.

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: 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.

The next document explains how the configurations can be managed and other actions you can perform through SSO configurations.

Was this article helpful?