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://login.xecurify.com/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: Restricting access by Limiting the number of devices

Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. When Device for a policy is enabled, the Enduser's device will be matched to previously registered device for that user. The end users will be able to access services provided by us on this fixed no. of devices of that particular user.

• Go to Adaptive Authentication from the left navigation bar.
• Click on Add Policy tab.



• Add a Policy Name for your Adaptive Authentication Policy.



• Scroll down to Device Configuration section and click on Edit.
• Enter the Number of Devices which are allowed to register in field Number of Device Registrations Allowed.



• You can enable or disable the Mobile Device Restriction to ensure if the login attempts from mobile devices will be accepted or declined.
• Similarly, you can enable or disable MAC Address Based Restriction.



• Now, scroll down to the Action For Behaviour Change section and click on Edit. Select the action you want to perform if the IP address is out of the range. i.e. Allow, Challenge or Deny.




Action for behavior Change Options :




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




Challenge Type Options :




Attribute	Description
User second Factor	The User needs to authenticate using the second factor he has opted or assigned for such as OTP over SMS PUSH Notification OTP over Email And 12 more methods.
KBA (Knowledge-based authentication)	The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further.
OTP over Alternate Email	User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further.



• Scroll to the end and click on save.

4. Enable Restriction for Google Apps

• Go to Policies >> App Login Policy from the left navigation bar.
• Click on Edit option against your selected app.



• Set your application name in the Application and select password as Login Method.
• Enable Adaptive Authentication.
• From the Select Login Policy dropdown, select the policy we created in the last step and select the required restriction method as an option.
• Click Save.




How to add a trusted Device

1. When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

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.