Need Help? We are right here!
Thanks for your Enquiry. Our team will soon reach out to you.
If you don't hear from us within 24 hours, please feel free to send a follow-up email to info@xecurify.com
Search Results:
×Two-Factor Authentication (2FA) or Multi-factor Authentication is the process of the authentication in which you have to provide two factors to gain the access into a particular application. First Factor is the one that you know username and password and Second factor is what you might have as unique, like a phone (For OTP) or Fingerprint. This additional layer of security prevents the unauthorized person from accessing the resources even if they know your username and password. miniOrange provides 15+ authentication methods and solutions to secure your applications.
For web applications that do not provide support for federated single sign-on, we have miniOrange Secure Single Sign-On browser plugins for SSO. Here, it is enabled on an application, where end users see an icon on their home pages and browsers, through this users can set and update their credentials. ( In the secure store for that application only).
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, OpenLDAP, AWS etc), Identity Providers (like Microsoft Entra ID, Okta, AWS), and many more. You can configure your existing directory/user store or add users in miniOrange.



| App details | Description |
| Group Name | Select Group name as default.(This will allow all your added groups to access this service) |
| Policy Name | Select Policy Name the same as your application name. |
| Individual Login | If each user has a different username and password for the app, admin should choose an Individual Login Account option, so that users can save their username and password from the user portal themselves. |
| Shared Login | If multiple users are allowed to access the app via the same credentials assigned by admin, admin should choose share Login Account option. |









| App Type | Description |
| SIMPLE LOGIN | When its a Simple form with Username, password and a button to Login |
| LOGIN_WITH_DOMAIN | When along with username and password, there is another field that requires input (constant like account id or domain) |
| LOGIN_AFTER_CLICK | When the login form loads after a button click only. |
| LOGIN_SECOND_PAGE | 1. When username and password are on separate pages[2 page form]. 2. When username and password are on separate pages and also have separate buttons on each page (Separate button means that they cant be identified with a common query). Submit Button Field :Query Format document.querySelector(username-query) == null ? document.querySelector(button-1 query); document.querySelector(password-query).parentElement.parentElement.parentElement.querySelector(button-2 query) For ex:- 1. username-query :- Insert query selector of selecting username with unique attributes[id ,class, name , type] 2. password-query :- Insert query selector of selecting password with unique attributes[id ,name , type] 3. button-1 query, button-2 query :- insert query selector of selecting button with unique attributes[ class,name, type] |
| LOGIN_WITH_PRE_CLICK | When a click is required before submitting the form. E.g, Some checkbox needs to be clicked. |
| App details | Description |
| Group Name | Select Group name as default.(This will allow all your added groups to access this service) |
| Policy Name | Select Policy Name the same as your application name. |
| Individual Login | If each user has a different username and password for the app, admin should choose an Individual Login Account option, so that users can save their username and password from the user portal themselves. |
| Shared Login | If multiple users are allowed to access the app via the same credentials assigned by admin, admin should choose share Login Account option. |








3.1: Enable 2FA for Users of Evernote app


3.2: Configure 2FA for your Endusers

3.3: Enduser 2FA Setup










Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.
Adaptive Authentication for Evernote enables administrators to enforce context-aware access policies by evaluating user login conditions such as IP address, device, location and login time. Based on the configured policy, users can be allowed access, challenged with additional verification or denied access. Administrators can also configure email alerts, customize user-facing error messages, review policy settings before deployment and assign adaptive authentication policies to application login policies to strengthen security and prevent unauthorized access.
[Note: The Adaptive Authentication section has been moved from the left navigation menu. You can now access and manage adaptive authentication policies by navigating to Policies >> Adaptive Access Policy.]
A. Restricting access to Evernote with IP Based Access 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.
You can configure Adaptive Authentication with IP Based Restriction in following way :






| Attribute | Description |
|---|---|
| Allow | Allow users to authenticate and use services if Adaptive authentication condition is true. |
| Deny | Deny user authentications and access to services if Adaptive authentication condition is true. |
| Challenge | Challenge users with one of the three methods mentioned below for verifying user authenticity. |
| Attribute | Description |
|---|---|
| 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 the user for 2 of 3 questions he has configured in his Self-Service Console. Only after the right answer to both questions is the user 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. |
B. Restricting access to Evernote with Device Based Access Restriction
Device Based Access Restriction allows administrators to control user access based on trusted and registered devices. By leveraging device identification and verification mechanisms, administrators can define policies that evaluate the device used during authentication. When a user attempts to log in, the device is assessed against the configured policy and the appropriate action: Allow, Challenge or Deny is applied based on the configured conditions.
You can configure Adaptive Authentication with Device Based Restriction in following way :






C. Restricting access to Evernote with Location Based Access Restriction
In location restrictions, admin configures a list of locations where they want to allow end-users to either login or deny based on the condition set by the admin. When a user tries to login with adaptive authentication enabled, their Location Attributes, such as (Latitude, Longitude and Country Code) are verified against the Location list configured by the admin. Based on this user will be either allowed, challenged or denied.
You can configure Adaptive Authentication with Location Based Restriction in following way :






D. Restricting access to Evernote with Time Based Access Restriction
In time restriction, admin configures a time zone with Start and End Times for that timezone and users are either allowed, denied or challenged based on the condition in the policy. When an end-user tries to login with the adaptive authentication enabled, their time zone-related attributes such as Time-Zone and Current System Time, are verified against the list configured by the admin and based on the configuration, the user is either allowed, denied or challenged.
You can configure Adaptive Authentication with Time Based Restriction in following way :






E. Email Alerts and Custom Email Message
This section handles the notifications and alerts related to Adaptive Access Policy. It provides the following 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. |


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




