How to Enable IP Restriction | Device Restriction | Location Restriction | Time Of Access Restriction for Google Apps (G Suite)?

Follow the Step-by-Step Guide given below for Google Apps (G Suite) Single Sign-On (SSO)

Step 1: Configure Google Apps (G Suite) in miniOrange

• Login into miniOrange Admin Console.
• Go to Apps >> Manage Apps.



• Click on Add Applicaton button.



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



• In the next step, search for your application from the list, if your application is not found. Search for "custom" and you can set up your app via Custom SAML App.

• Enter the SP Entity ID or Issuer as google.com.
• Enter the ACS URL as https://www.google.com/a/[domain_name]/acs.
• Enter the Single Logout URL as https://mail.google.com/a/out/tld/?logout.
• 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).
• Leave the Attributes section empty.



• Go to the Add Policy and select DEFAULT from the Group Name dropdown.
• Now enter the name for your app authentication policy in the Policy Name field.
• Select PASSWORD from the First Factor Type dropdown.
• Click on Save to add Google Apps (G Suite).



• Click on Metadata link to download the metadata which will be required later. Click on Link to see the IDP initiated SSO link for Google Apps (G Suite).



• Keep SAML Login URL , SAML Logout URL and click on the Download Certificate button which you will require in Step 4.

Step 2: Choose Your User Directory

2.1: Setup AD as User Directory

1. Login to miniOrange dashboard from the Admin Console.
2. From the left side menu, click on User Stores >> Add User Store.



3. Select User Store type as AD/LDAP.



1. STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
2. STORE LDAP CONFIGURATION ON PREMISE: Choose this option if you want to keep your configuration in your premise and only allow access to AD inside premises. You will have to download and install miniOrange gateway in your premise.




4. Enter LDAP Display Name and LDAP Identifier name.
5. Select Directory Type as Active Directory.
6. Enter the LDAP Server URL or IP Address against LDAP Server URL field.
7. Click on Test Connection button to verify if you have made a successful connection with your LDAP server.



8. In Active Directory, go to the properties of user containers/OU's and search for Distinguished Name attribute.



9. Enter the valid Bind account Password.
10. Click on Test Bind Account Credentials button to verify your LDAP Bind credentials for LDAP connection.



11. Search Base is the location in the directory where the search for a user begins. You will get this from the same place you got your Distinguished name.



12. Select a suitable Search filter from the drop down menu. To use custom Search Filter select "Custom Search Filter" option and customize it accordingly.



13. You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Save button to add user store.




Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.

Attribute	Description
Activate LDAP	All user authentications will be done with LDAP credentials if you Activate it
Sync users in miniOrange	Users will be created in miniOrange after authentication with LDAP
Backup Authentication	If LDAP credentials fail then user will be authenticated through miniOrange
Allow users to change password	This allows your users to change their password. It updates the new credentials in your LDAP server
Enable administrator login	On enabling this, your miniOrange Administrator login authenticates using your LDAP server
Show IdP to users	If you enable this option, this IdP will be visible to users
Send Configured Attributes	If you enable this option, then only the attributes configured below will be sent in attributes at the time of login



14. Click on Save. After this, it will show you the list of User stores. Click on Test Configuration to check whether you have enter valid details. For that, it will ask for username and password.



15. On Successful connection with LDAP Server, a success message is shown.
16. Click on Test Attribute Mapping.



17. Enter a valid Username. Then, click on Test. Mapped Attributes corresponding to the user are fetched.



18. After successful Attribute Mapping Configuration, go back to the ldap configuration and enable Activate LDAP in order to authenticate users from AD/LDAP.

Refer our guide to setup LDAPS on windows server.

2.2: Setup miniOrange as a User Store

1. Log in to miniOrange Admin Console.
2. There are 3 ways to setup miniOrange as an Identity Source

2.2.1 Create User in miniOrange

2.2.2 Bulk Upload Users

2.2.3 Self User Registration

2.2.1 Create User in miniOrange

• Click on Users >> Add User.



• Here, fill the user details without the password and then click on the Create User button.



• After successful user creation a notification message "An end user is added successfully" will be displayed at the top of the dashboard.



• Click on On Boarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.



• Now, Open your email id. Open the mail you get from miniOrange and then click on the link to set your account password.
• On the next screen, enter the password and confirm password and then click on the Single Sign-On (SSO) reset password button.



• Now, you can log in into miniOrange account by entering your credentials.

2.2.2 Bulk Upload Users in miniOrange via Uploading CSV File.

• Navigate to Users >> User List. Click on Add User button.



• In Bulk User Registration Download sample csv format from our console and edit this csv file according to the instructions.



• To bulk upload users, choose the file make sure it is in comma separated .csv file format then click on Upload.



• After uploading the csv file successfully, you will see a success message with a link.
• Click on that link you will see list of users to send activation mail. Select users to send activation mail and click on Send Activation Mail. An activation mail will be sent to the selected users.

2.2.3 Self User Registration

• miniOrange self user registration allows end users to register themselves using customized registration form. miniOrange admin users can customize the registration form by adding more custom fields according to their choice. Follow the miniOrange guide to customize user self registration page.

Step 3: Setup SSO in Google Apps (G Suite) Admin Account

• Now login to Google Admin Console and Select Security Tab from Admin Console.



• From listed options select Set Up Single Sign-On (SSO) with a third party idp.



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

Step 4: Login to your Google Apps (G Suite) account with miniOrange IdP by either of the two steps:

Using SP Initiated Login

1. Go to your Google Apps (G Suite) URL, enter your credentials then click on Login. Now you will be redirected to miniOrange IdP Sign On Page.



2. Enter your miniOrange login credential and click on Login. You will be automatically logged in to your Google Apps (G Suite) account.

Using IDP Initiated Login

1. Login to miniOrange IdP using admin credentials and select the User Dashboard from the right side menu.



2. Click on Google Apps (G Suite) application which you added, to verify your SSO configuration.

Step 5: Adaptive Authentication with Google Apps (G Suite)

5.1: Restricting access to Google Apps (G Suite) with IP Blocking

You can use adaptive authentication with Google Apps (G Suite) Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

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

• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.



• Select your Action for behaviour Change and Challenge Type for user from the Action for behaviour Change Section.





Action for behaviour Change Options :




Attribute	Description
Allow	Allow user to authenticate and use services if Adaptive authentication condition is true.
Challenge	Challenege 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 Notofication 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 recieve 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.



• Now 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 +.
• Scroll to the end and click on save.

5.2: Adaptive Authentication with Limiting 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. The end users wii be able to access services provided by us on this fixed no. of devices.

You can cofigure Adaptive Authentication with Device Restriction in follwing way


• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behaviour Change and Challenge Type for user from the Action for behaviour Change Section.




• Scroll down to Device Configuration section and enable Allow User to Register Device option to allow users to register their devices.
• Enter the Number of Devices which are allowed to register in field next to Number of Device Registrations Allowed
• Choose Action if number of devices exceeded (This will override your setting for Action for Behaviour Change.)
1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
2. Deny : Deny users access to the system
• Enable option Send email alerts to Users if number of Device registrations exceeded allowed count if you want to alert the user about no of devices exceeding the limit. Save the configuration.

5.3: Add Adaptive Authentication policy to Google Apps (G Suite).

• Login to Self Service Console >> Policies.
• Click on Edit option for predefined SAML app policy.



• Set your application name in the Application and select password as Login Method.
• Enable Adaptive Authentication on Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step and click on 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.

More Secure authentication with Two-Factor Authentication

The most practical way to strengthen authentication is to require a second factor after the username/password stage. Since a password is something that a user knows, ensuring that the user also has something or using biometrics thwarts attackers that steal or gain access to passwords.

Traditional two-factor authentication solutions use hardware tokens (or "fobs") that users carry on their keychains. These tokens generate one-time passwords for the second stage of the login process. However, hardware tokens can cost up to $40 each. It takes time and effort to distribute them, tracks who has which one, and replace them when they break. They're easy to lose, hard to use, and users consistently report high levels of frustration with token-based systems.

Your choice of the second factor

miniOrange authentication service has 15+ authentication methods.

• One time passcodes (OTP) over SMS
• OTP over SMS and Email
• Out of Band SMS and Email
• Soft Token
• Push Notification
• USB based Hardware token
• Security Questions
• Mobile Authentication
• Voice Authentication (Biometrics)
• Certificate Authentication
• Device Identification
• Location
• Time of Access
• User Behavior

You can choose from any of the above authentication methods to augment your password based authentication. miniOrange authentication service works with all phone types, from landlines to smart-phone platforms. In the simplest case, users just answer a phone call and press a button to authenticate. miniOrange authentication service works internationally and has customers authenticating from many countries around the world.

For further details refer :
https://developers.google.com/google-apps/sso/saml_reference_implementation
https://support.google.com/a/answer/60224?hl=en