iPipeline

miniOrange provides secure access to Ipipleine for enterprises and full control over access of iPipeline application. Single Sign On (SSO) into your iPipeline Account with one set of login credentials.

miniOrange Identity Management Features

• Single Sign-On

  miniOrange Single Sign-On (SSO) Solution provides easy and seamless access to all enterprise resources with one set of credentials. miniOrange also provides secure authentication by establishing a trust relationship between the Service Provider and Identity Provider. miniOrange Single Sign-On supports SSO to any type of device or application whether they are in the cloud or on-premise. Learn More

• Multi-factor Authentication

  Secure your iPipeline application from password theft using multi-factor authentication methods with 15+ authentication types provided by miniOrange. Our multi-factor authentication methods prevent unauthorized users from accessing information and resources having passwords alone as an authentication factor. Enabling second-factor authentication for iPipeline protects you against password thefts. Learn More

• IP Blocking

  miniOrange provides IP blocking/IP restriction for iPipeline login which adds security to Gmail, Web, and other applications. In this, we provide you option for IP blocking which includes both automatic (based on user behavior) and manual IP blocking which includes blacklisting and whitelisting of IP addresses to provide access restriction, the office only access, intranet access & network restriction. Learn More

• Adaptive Authentication

  miniOrange Adaptive Authentication aims to provide a better experience to reduce the authentication burden on users while enforcing strong authentication where it is needed the most. For example, when a user attempts to access an application via an unregistered device then they may be prompted to register it. If the user logs in from a geographical location other than their office, they may be asked to answer security questions. Learn More

• User Provisioning

  miniOrange User Provisioning provides an easy way of creation, management, and maintenance of end-users especially for large enterprises to reduce the risk for unauthorized access of information. User provisioning includes the creation, updating and deletion of user accounts. User provisioning makes life easier for admins because they do not have to manually arrange access for each user. Learn More

miniOrange supports both IdP (Identity Provider) and SP (Service Provider) initiated Single Sign On (SSO)

• IdP Initiated Single Sign On (SSO)

  In IdP Initiated Login, SAML request is initiated from miniOrange IdP.

• Enduser first authenticates through miniOrange Idp by login into miniOrange Self Service Console.
• The Enduser will be redirected to their iPipeline account by clicking the iPipeline icon on the Enduser Dashboard - there is no need to log in again.

• SP Initiated Single Sign On (SSO)

  In SP Initiated Login, SAML request is initiated by iPipeline.

• An Enduser tries to access their Account by going to iPipeline domain.
• They will be redirected to miniOrange Self Service Console.
• Here they can enter the miniOrange login credentials and login to their iPipeline Account.

Follow the Step-by-Step Guide given below for iPipeline Single Sign On (SSO)

Step 1: Configure miniOrange Settings for iPipeline

• Log in as a customer from the Admin Console.
• Go to Apps >> Manage Apps. Click Configure Apps button.



• Click on the SAML tab. Search for iPipeline app. You will see the below screen.

• Select the iPipeline app. Enter following details :

Custom Application Name	Choose appropriate name according to your choice
SP Entity ID or Issuer	Contact iPipeline support for Entity ID
ACS URL	https://federate-uat.iPipeline.com/sp/ACS.saml2
NameID	Email Address
NameID format	Select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

You need to configure bellow attributes by clicking on Add Attributes .

AttributeName	Description	Values
CompanyIdentifier	Mandatory. Used to determine Username	Example: 1234
ChannelName	Mandatory. Used to determine Username	Example: ABC
Action	Mandatory. Used to tell service what action to take. Like (CREATE)	Example: CREATE
Groups	Mandatory. Defines Group user is associated with and what systems user has access to.	Example: 01234-UsersGroup
TimeOutUrl	Mandatory. The attribute name must be present but the value of this attribute is no longer used. An empty or null value for this attribute is required
ApplcationData	Mandatory. The attribute name should be present but an empty value for this attribute is allowed.

Click on + to add atrributes.

• Fill attribute name. For example- CompanyIdentifier
• Select attribut value as Custom Profile Attribute.
• From dropdown select Custome Attribute 1 for first custom profile attribute.

Likewise you can configre all six custom attributes. After configuring, it will look like the image shown below.

Now fill Group, Policy and Login Method related details. For that you can refer above image.

• Group Name as DEFAULT.
• Fill Policy Name in policy tab.
• Set First Factor Type as password and hit the save button.

After saving the app details, an app will be configured in miniorange with metadata as you can see in below image -

• Click on ‘metadata’ which will take you to idp metadata page.

• Download the Metadata as shown above and send it to your contact in iPipeline so that they can active SAML SSO for your account.

Step 2: Choose Your User Directory

2.1: Setup AD as User Directory

• Login to miniOrange dashboard from the Admin Console.
• Click on Identity Providers >> Add Identity Provider in the left menu of the dashboard.



• In Choose Identity Provider, select AD/LDAP Directories from the dropdown.



• Then search for AD/LDAP and click it.



• STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If the active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
• 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 on your premise.




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



• In Active Directory, go to the properties of user containers/OU's and search for the Distinguished Name attribute. The bind account should have minimum required read privileges in Active Directory to allow directory lookups. If the use case involves provisioning (such as creating, updating, or deleting users or groups), the account must also be granted appropriate write permissions.



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



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



• Select a suitable Search filter from the drop-down menu. If you use User in Single Group Filter or User in Multiple Group Filter, replace the <group-dn> in the search filter with the distinguished name of the group in which your users are present. To use custom Search Filter select "Write your Custom Filter" option and customize it accordingly.



• Click on the Next button, or go to the Login Options tab.
• You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Next 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
Fallback Authentication	If LDAP credentials fail then user will be authenticated through miniOrange
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
Sync users in miniOrange	Users will be created in miniOrange after authentication with LDAP

• Click on the Next button, or go to the Attributes tab.

Attributes Mapping from AD

• By default userName, firstName, lastName, email are configured. Scroll down and click on Save button. To fetch additional attributes from Active Directory, enable Send Configured Attributes. On the left side, enter the name that you wish to release to the applications. On the right side, enter the attribute name from Active Directory. E.g., if you wish to fetch company attribute from Active Directory, and send it as organization to configured applications, enter the following:

  Attribute Name sent to SP = organization
  Attribute Name from IDP = company






• Click on the Next button, or go to the Provisioning tab.

User Import and Provisioning from AD

• If you want to set up provisioning, click here for detailed information. We will skip this step for now.




Test Connections

• You will see a list of directories under Identity Providers. From the dropdown, select AD/LDAP Directories, search for your configured directory, click the three dots next to it, and select Test Connection.



• A pop-up appears prompting you to enter a username and password to verify your LDAP configuration.



• On Successful connection with LDAP Server, a success message is shown.




Test Attribute Mapping

• You will see a list of directories under Identity Providers. From the dropdown, select AD/LDAP Directories, search for your configured directory, click the three dots next to it, and select Test Attribute Mapping.



• A pop‑up appears to enter a username and click Test.



• The Test Attribute Mapping Result will be displayed.




Set up AD as External Directory configuration is complete.




Note: Refer our guide to setup LDAP 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 Onboarding 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.



3. Configure Adaptive Authentication Policy

• 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

a. Configure IP Restriction

IP Based Access Restriction allows administrators to control user access based on the source IP address of the login request. Administrators can configure trusted or restricted IP addresses and IP ranges and define the action to be taken when a user's IP address matches the configured criteria. During authentication, the user's IP address is evaluated against the configured policy and access is either Allowed, Denied or Challenged based on the selected configuration.

• Expand the IP Based Access Restriction section by clicking on the dropdown icon to configure IP-based access rules.



• Click Add IP Range to configure IP addresses or IP ranges for the policy.



• Specify the IP Address that you want to whitelist. For the IP Range other than the whitelisted one, you can select the above setting to reflect.
• Choose either Allow or Deny by selecting the corresponding option from the dropdown. If a user tries to login with the whitelisted IP address, they will always be allowed access.
• We support IP address range in three formats i.e., IPv4, IPv4 CIDR and IPv6 CIDR. You can choose whichever is suitable for you from the dropdown menu.
• You can add multiple IPs or IP ranges by clicking the + Add IP Range button.



• Once the changes are made, click on Next.

b. Configure Device Restriction

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.

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






c. Configure Location Restriction

In location restrictions, the admin configures a list of locations where they want to allow or deny end-user access based on the condition set by the admin. When a user tries to log in with Adaptive Access Policy enabled, their location attributes, such as latitude, longitude and country code, are verified against the location list configured by the admin. Based on this, the user will be either allowed, challenged or denied.

• Expand the Location Based Access Restriction section by clicking on the dropdown icon to configure Location Based Access Restriction rules.
• Click on Add Location.



• In the Enter Location input field, enter the Location Name and then select the correct location from the search results using the UP & DOWN navigation keys.
• Add the In and Around Distance for your location in the next input field. This will be the total area in and around the location we have configured using the Latitude and Longitude points.
• In the next select list, select your distance parameter as either KMS (Kilometers) or Miles. For each location you add, you can choose to either allow or deny it by enabling or disabling the switch button next to it.
• You can click on the Add Location to add more than one location.



• Save the changes you made by scrolling down at the bottom of the page.

d. Configure Time Restriction

In time restriction, the admin configures a time zone with start and end times and users are either allowed, denied or challenged based on the condition in the policy. When an end-user tries to log in with Adaptive Access Policy enabled, their time zone-related attributes, such as time zone and current system time, are verified against the list configured by the admin. Based on the configuration, the user is either allowed, denied or challenged.

• Expand the Time Based Access Restriction section by clicking on the dropdown icon to configure Time Based Access Restriction rules.



• Click on Add Time.



• From the Select Timezone list, select the timezone. From the Start Time and End Time lists, select the appropriate values. For each time configuration you add, use the dropdown menu to select whether to Allow or Deny it.



• Enter the value in minutes in the input field next to the Login Window Buffer Time (Minutes). This value allows you to specify some relaxation before your start time and after your end time. (so if the start time is 6 AM and the end time is 6 PM with a time difference value set to 30 minutes, then the policy will consider the time from 5:30 AM to 6:30 PM). If no value is entered in this field, the default value is set which is 0 minutes.
• You can click on the Add Time button to include more than one Time Configuration and then follow the above step.
• Click on Next.

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.




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.