Enable Device Restriction for Google Workspace (G Suite)

1. Configure Google Workspace (G Suite) in miniOrange

• Log into miniOrange Admin Console.
• Go to Apps and click on Add Applicaton button.



• In Choose Application Type click on Create App button in SAML/WS-FED application type.



• Search for the Google in the list.



• Enter your Domain name that you uses with the Google Workspace.
• Enter the Single Logout URL as https://mail.google.com/a/out/tld/?logout.
• From the Provisioning tab, enter the Domain Administrator in Google Apps (G Suite) Administrator field and click on "Verify Google Apps Administrator" to verify if the domain entered is of administrator (this is an optional field).



• Click on Save.

Get IdP Metadata Details to upload to Google Apps:

• Go to Apps >> Manage Apps.
• Search for your app and click on the select in action menu against your app.
• Click on Metadata to get metadata details, which will be required later. Click on Show SSO Link to see the IDP initiated SSO link for Google Apps.



• Here you will see 2 options, if you are setting up miniOrange as IDP copy the metadata details related to miniOrange, if you required to be authenticated via external IDP's (OKTA, AZURE AD, ADFS, ONELOGIN, GOOGLE APPS) you can get metadata from the 2nd Section as shown below.



• Keep SAML Login URL and click on the Download Certificate button to download certificate which you will require in Step 2.

2. Configure SAML SSO in Google Workspace (G Suite)

• Now login to Google Admin Console and Select Security Tab from Admin Console.
• Go to Authentication >> SSO with third-party IDP. Here, from the SSO profile for your organization section, click on the edit icon.





• Enable the Setup SSO with third party identity provider checkbox.
• Enter Sign-In Page URL: SAML Login URL from Step 1.
• Enter Sign-Out Page URL: < Base Server Url > /idp/oidc/logout?post_logout_redirect_uri=https://gmail.com
  Example: https://test.miniorange.in/moas/idp/oidc/logout?post_logout_redirect_uri=https://gmail.com
  
• Upload the certificate by clicking on Replace Certificate link that was downloaded earlier in Step 1.
• Enter Change Password URL: SAML Login URL from Step 1.
• Save the settings.
• Your Google SSO SAML integration is done.



2.1. Assign SSO profile to organizational units or groups:




If you want some of your users to sign in to Google directly, you can move those users into an organizational unit (OU) or group. Then, manage SSO settings for the OU or group so that those users are authenticated by Google rather than using your third-party IdP. Follow the following steps:

• If you want all your (non-super admin) users to sign in using a third-party IdP : You don't need to manage.
• If you want some of your users to sign in to Google directly : Click Manage SSO profile assignments and continue to the next step.
  • If you are assigning the SSO profile for the first time, then click Get started. Otherwise, click Manage. Note: Get started is only available if you’ve already enabled your third-party SSO profile.
  
  
  
  
  • Select the organizational unit or group for which you’re assigning the SSO profile from the left .
    Note: If the SSO profile assignment for an OU or group differs from your domain-wide profile assignment,
an override warning appears when you select that OU or group. You can’t assign the SSO profile on a
per-user basis. The Users view let you check the setting for a specific user.
    
  
  
  
  • Choose Organization's third Party SSO Profile if you want your users in the OU or group to sign in to Google services using the IdP designated in your domain’s third-party SSO profile.
  • Choose None if you want your users in the OU or group to sign in directly with Google.
  • Choose Another SSO profile in case you already have another Identity Provider configured and would like to use it for user authentication.
  • Then click Save.

2.2. To turn SSO off for all users:

If you want to turn off the third-party authentication for all your users without changing the SSO profile assignment for OUs or groups, you can disable the third-party SSO profile:

• Uncheck Set up SSO with third-party identity provider.
• Click Save.

3. Configure Device Restriction Policy

Device restriction lets admins control application access using device trust. You can use Agentless Device Restriction (browser-based fingerprinting) or Agent-Based Device Restriction (installed agent with risk scoring) depending on your security requirements.

• Login to Self Service Console >> Policies >> Adaptive Access Policy section from the left side menu.



• Click on the Create Policy button on the upper right. Add a suitable policy name and click on Create Policy.

3.1 Policy Overview

• Enable the Device Configuration toggle.



• You can configure device restriction using either Agentless or Agent-Based methods:

Agentless Device Restriction

• Number of Device Registrations Allowed: Specifies the maximum number of devices a user can register.
• Enable Mobile Device Restriction: Blocks login attempts from mobile devices.
• Enable Device Auto-Registration: Allows automatic device registration.




Agent-Based Device Restriction

• Prerequisites for enabling Agent-Based Device Restriction:
• All end users must install the Device Agent on their devices before accessing the application.
• Users without the agent are blocked and see: Please install the miniOrange Device Agent on your device and try again.
• The Device Agent is currently supported on Windows devices only.
• Click Download Agent to get the installation file for end users.
• Under Device Registration Method, choose one of the following:
• Self Registration by User: Users can register their own devices up to the defined limit. Provides flexibility with moderate security.



• Number of Device Registrations Allowed: Specifies the maximum number of devices a user can register.
• Enable Mobile Device Restriction: Blocks login attempts from mobile devices.
• Enable Device Auto-Registration: Allows automatic device registration.
• Pre-Approved Trusted Devices Only: Higher security. The admin manually manages trusted device information. Select this option and click Upload Pre-Approved Trusted Devices (CSV) to import devices (you can skip this step if devices are already uploaded).



• Upload a CSV file containing pre-approved users and devices (users must already exist in miniOrange). Download Sample CSV for reference.
• Configure the following options:
• Enable Mobile Device Restriction: Blocks login attempts from mobile devices.
• Enable Device Auto-Registration: Allows automatic device registration.
• Configure Risk Engine for Device Trust Evaluation

  The Risk Engine allows you to evaluate device trustworthiness by analyzing multiple device attributes and calculating a risk score. Based on this score, user access is allowed, challenged or denied during login and device registration.

• Navigate to the Risk Engine section and click Configure.



• Configure Risk Parameters:
• In the Risk Parameters tab, review the list of device attributes grouped by category.
• The Device Identifiers category contains mandatory attributes (such as Installation ID, BIOS UUID, Machine SID, etc.). These attributes are always enabled and cannot be disabled or reprioritized, as they are critical for device fingerprinting.
• For other categories (Hardware, Network, Software, Location), enable the attributes you want to use for device trust evaluation.
• Set a Priority for each enabled attribute:
• High: Strong impact on risk score
• Medium: Moderate impact
• Low: Minimal impact



• Click on Save Changes.
• Configure Risk Score
• In the Risk Score, define the score ranges (0–100) that determine the authentication outcome during user login.
• Lower risk scores indicate trusted devices.
• Higher risk scores indicate potential security risks or anomalies.
• Configure the thresholds as follows:
• Allow: Allow user to authenticate without challenge and registration.
• Challenge: Allow user authentication with a challenge, e.g., when the device limit is exceeded.
• Deny: Deny user authentication, e.g., when the device limit is exceeded, when device attribute is mismatch.

3.2 Action for Behavior Change

• You can configure one of the three possible actions for your Adaptive Access Policy as explained below:




Attribute	Description
Allow	Allow users to authenticate and use services if Adaptive Access Policy condition is true.
Deny	Deny user authentications and access to services if Adaptive Access Policy condition is true.
Challenge	Challenge users with one of the three methods mentioned below for verifying user authenticity.




Challenge Type Options:




Factors	Description
User Second Factor	The user needs to authenticate using the second factor they have selected or been assigned, such as OTP over SMS PUSH Notification OTP over Email and many more.
KBA	The system will ask the user for 2 of 3 questions they have configured in their Self-Service Console. Only after the correct answers to both questions will the user be allowed to proceed further.
OTP over Alternate Email	User will receive an OTP on the alternate email they have configured through the Self Service Console. Once the user provides the correct OTP, they are allowed to proceed further.

3.3 Email Alerts and Custom Error Message

This section handles the notifications and alerts related to Adaptive Authentication. It provides the following options:

• Send email alerts: Configure the recipients who should receive email notifications when adaptive authentication events occur. Alerts can be sent to administrators, end users or both, depending on your monitoring and security requirements.
• Send email alerts to administrators: Enable this option to notify administrators when configured adaptive authentication events are triggered. You can optionally specify an email address under Administrator's e-mail address to receive alerts to receive alerts; otherwise, alerts are sent to the default administrator account.



• Send email alerts to end users: Enable this option to notify end users when adaptive authentication events affect their login attempts or device registrations.
• Number of Device Registrations Exceeded Allowed Count: When enabled, end users receive an email notification if they attempt to register more devices than the maximum number allowed by the configured device restriction policy. (Available only for end-user notifications.)



• Get email alerts if users login from unknown devices or locations: Admins need to enable this option to enable receiving alerts for different alert options.



Option	Description
Users login from unknown IP addresses, devices or locations	Enabling this option allows you to login from unknown IP addresses or devices and even locations.
Challenge Completed and Device Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
Challenge Completed but Device Not Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
Challenge Failed	Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.





• In case you want multiple admin accounts to receive alerts, then you can enable the option for admin and then enter the admin emails separated by a ',' in the input field next to Administrator's email to receive alerts label. To enable alerts for the end users, you can enable the End User checkbox.
• In case you want to customize the deny message that the end user receives in case his authentication is denied due to adaptive policy, you can do this by entering the message inside Deny Message text box.

3.4 Review

Review the configured policy conditions, behavior change actions, email alert settings and custom error messages before creating the adaptive authentication policy. This step provides a consolidated view of all configured settings, allowing you to verify the policy configuration and make any necessary changes before saving.

• Once you have verified all configurations, click Create Policy to save and activate the policy.
• You will see the policy listed once it’s successfully added.

4. Enable Restriction for Google Workspace (G Suite)

• Login to Self Service Console >> Policies >> App Login Policy.
• Click on the Edit icon for the predefined app policy.



• Set Group Name and Policy Name as required. Select Password as First Factor.



• Enable Adaptive Authentication on Edit Login Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step.
• Apply Restrictions Using: Select how IP Restriction should be evaluated when multiple adaptive authentication restrictions are configured.
  • AND: The configured IP Restriction and all other enabled restrictions must be satisfied before access is granted.
  • OR: The configured IP Restriction or at least one other enabled restriction must be satisfied before access is granted.



• Adaptive Authentication Restrictions: Configure additional login restrictions and verification conditions along with the existing configured Restriction to strengthen account security and control user access based on contextual risk factors.

1. Register your organization with Android Enterprise.

• Login into miniOrange MDM dashboard by clicking here.



• Once logged in, Navigate to ANDROID -> Android Enterprise and click on Register button. You will need to Register your organization with Android Enterprise initially and this will be a one-time process.



• Click here for detailed instructions on registering your organization with Android Enterprise.

2. Create a new policy

• Go to ANDROID -> Policies in the miniOrange MDM dashboard. Here the default policy is already created for you with no Play Store apps added. You can use this policy to get the device enrolled without giving access to any application.
• Click the Create Policy button to design a new policy.



• Now, go to the Application section and choose the specific Google Workspace applications for which you want to get installed on the approved devices.
• Double-check all the previous settings. Once done, click on the Create Policy button to finalize the policy.



• Similarly, you can create multiple policies with different application sets and restrictions that can get attached to the mobile device based on its device approval status, e.g. PENDING, USER MFA COMPLETED, ADMIN APPROVED, etc

3. Attach Policy to Device Group

• Go to ANDROID -> Device Groups, click on Add Group to create a group for approved devices.
• Attach the newly created policy to the selected device group. This will ensure that the policy is enforced for all devices within that group.

4. Configure device enrollment settings

• Go to ANDROID -> Devices, and click on Enroll to create the device enrollment token.



• Select the user whose device is going to be enrolled, the device ownership mode as Personal if the device is owned by the end-user or Corporate if the device is issued by the organization.



• If the device is going through the User or Admin verification flow as shown in the image above then it is recommended to do the initial enrollment with the default group and assign appropriate groups after verification.
• The example above has shown the device will be enrolled with default policy and initially will have no Play Store application. Once the user verification via the MFA method is completed the device will be added to the MFA_Completed group and the associated policy will be assigned.



Note

The default MFA method setup for the end user is fetched from the miniOrange IAM dashboard and accordingly the MFA will be initiated, e.g. OTP over Email/Push Notification, etc



• The enrollment option ‘By User Invite’ will send the device enrollment steps over email for the selected user. The option ‘By Myself’ will show the enrollment details on this same screen.

5. Admin approval for enrolled devices

• Based on the enrollment token settings, the enrolled device will be listed on the dashboard. We can check the current status of the device in the Device Approval column where it is listed for Admin to approve, approved, MFA verification pending, etc .



• After accessing the user, and device details, Admin can click on the Approve button to approve and assign appropriate policy to the device.