Need Help? We are right here!
miniOrange provides Identity & Access Management (IAM) for your Office 365 secured with NetSkope Reverse Proxy. miniOrange IAM solution is fully compatible with NetSkope as well as integrates with multiple third-party applications to provide a wide range of solutions for secure authentication. miniOrange is one trusted platform to secure your identity, from customers to your workforce with Single Sign-On (SSO), Multi-factor Authentication (MFA), Adaptive Authentication, User Provisioning, Directory Authentication and more. We provide a centralized platform with enhanced capabilities for access management and identity management which fits almost any use case and can integrate with any system and any third-party application.
miniOrange IDP is compliant with NetSkope SAML Proxy and can enable sso into any third-party application connected via NetSkope.
NetSkope uses SAML-based SSO. NetSkope SAML proxy is required to direct the cloud app traffic sanctioned by your organization to the reverse proxy running in your tenant instance in the NetSkope cloud.
When an end user goes to a SaaS application, end user traffic is redirected to miniOrange via SAML for user authentication. Once that user is authenticated, traffic is redirected to the NetSkope reverse proxy engine for further analysis.
This document provides instructions to configure NetSkope as SAML Proxy to direct your configured Office 365 application traffic to the reverse proxy running in a customer’s tenant instance in the NetSkope cloud. In this case miniOrange is the IdP (Identity Provider) and the Office 365 is the SP (Service Provider).
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Shibboleth, Ping, Okta, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more.
|Custom Application Name||Application Name protected by NetSkope Reverse Proxy [E.g. Office 365]|
|SP Entity ID or Issuer||Organization ID that you copied from the NetSkope admin console [in Prerequisites]|
|ACS URL||SAML Proxy ACS URL that you copied from the NetSkope admin console [in Prerequisites]|
Get IdP Metadata Details to upload to NetSkope reverse proxy:
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.
1. Create User in miniOrange
2. Bulk Upload Users in miniOrange via Uploading CSV File.
Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.
|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|
|Fallback 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|
Refer our guide to setup LDAPS on windows server.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.
4.1: Enable 2FA for Users of NetSkope Reverse Proxy app
4.2: Configure 2FA for your Endusers
4.3: Enduser 2FA Setup
A. Restricting access to NetSkope Reverse Proxy with IP Blocking
You can use adaptive authentication with NetSkope Reverse Proxy 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:
|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.|
|User second Factor||The User needs to authenticate using the second factor he has opted or assigned for such as
|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.|
B. 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 will be able to access services provided by us on this fixed no. of devices.You can configure Adaptive Authentication with Device Restriction in following way
C. Add Adaptive Authentication policy to NetSkope Reverse Proxy.
D.Notification and Alert Message.
This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :
|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.|
Our Other Identity & Access Management Products