• Home
• App Integrations
• Adaptive Authentication
• IP restriction for Google Workspace (G Suite)

Enable IP Restriction for Google Workspace (G Suite)

---

miniOrange allows you to use IP Restriction policy to provide or deny access to the users based on trusted IP Addresses.

• For the IP Restriction to work, the Admin must create a policy specifying permitted IP addresses which allows the access to the application.
• Miniorange supports IP addresses range in three formats i.e. IPv4, IPv4 CIDR and IPv6 CIDR.
• To block the access, Admin must specify an action which needs to be performed when a user tries to login from a non trusted IP address (Such as Deny or Challenge the user with 2FA).
• Once the restriction policy is configured, it can be applied to any application’s login policy to enable IP restriction for that application

Follow the step-by-step guide given below to configure IP 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 IP Restriction: Restricting access with IP Blocking

You can allow a IP Address in certain range for SSO or you can deny it based on your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication based on different factors such as Device ID, Location, Time of Access, IP Address and many more, thus improving the security and functionality of Single Sign-On.

You can configure Adaptive Authentication with IP Blocking in following way:


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



• Enable Enable IP Restriction option from the IP RESTRICTION CONFIGURATION section to configure custom IP range.



• Select the Action you want to perform if the IP address is out of the range. i.e. Allow, Challenge & Deny.
• Specify the IP Address range for which you want above setting to reflect. You can add more than one IP Address ranges by clicking on following button +.
• We support IP addresses range in three formats i.e. IPv4, IPv4 CIDR and IPv6 CIDR. You can choose whichever is suitable for you from the dropdown menu.
• Now select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.





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 Conolse. 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 Workspace

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

External References

• Advanced security with IP Restrictions
• What is Adaptive Authentication? | Adaptive MFA
• Restrict user access to Google Workspace
• Google Workspace Single Sign-On
• How to block gmail access in office
• Why is it important to have a risk-based cybersecurity approach
• Device Restriction