• Home
• App Integrations
• Single Sign-On Integrations
• Qlik Cloud Single Sign-On

Qlik Cloud Single Sign-On SSO

---

Single Sign-On (SSO) solution by miniOrange provides secure Single Sign-On access into Qlik Cloud using a single set of login credentials. You can log into Qlik Cloud using miniOrange credentials or Azure AD credentials or any of your existing identity providers. With miniOrange SSO services, along with Qlik Cloud you can also login into other On-Premise and Cloud Applications using your existing Identity Providers/User Store (Azure Active Directory, Okta, Ping) credentials . Follow the given setup guide to integrate header-based SSO for your Qlik Cloud account.

miniOrange and Qlik Cloud Single Sign-On (SSO) integration supports the following features:

• SP Initiated Single Sign-On (SSO)

Follow the Step-by-Step Guide given below to Configure and tests Qlik Cloud Platform

1. Configure Qlik Cloud in miniOrange

• Login into miniOrange Admin Console.
• Go to Apps and click on Add Application button.



• Select OAuth/Openid as application type from All Apps dropdown.



• Search for Qlik Cloud in the list, if you don't find Qlik Cloud in the list then, search for OAuth2/OpenID Connect and you can set up your application via OAuth2/OpenID Connect.



• In the Basic tab, enter the following details:

Basic Tabs	Description
Display Name	Enter the Display Name (i.e., the name for this application).
Redirect URL	Copy the Redirect-URL from Qlik Cloud Application. You will get this URL when you create an application in the Qlik Cloud admin console.
Client ID	You can find Client ID by clicking the icon as shown below.
Client Secret	You can find Client Secret by clicking the icon as shown below.
Description (Optional)	Add a description if required.
Upload App Logo (Optional)	Upload an app logo (Optional). The app will be shown in the end-user dashboard with the logo that you configure here.




• Click on Save.
• You will be redirected to the Policies section.



• Click on the Assign group button. A new Configure Group Assignment Modal will open.
  • Assign Group: Select the groups you want to link with the application. You can select up to 20 groups at a time.
  
  
  
  • If you need to create new group. Click on Add New Group button.
  • Enter the Group name and click on Create Group.
  
  
  
  • Click on Next.
  • Assign Policies: Add the required policies to the selected groups. Enter the following details:
  • First Factor: Select the login method from the dropdown.
  • If you select Password as the login method, you can enable 2-Factor Authentication (MFA) and Adaptive Authentication, if needed.
  • If you select Password-less as login method, you can enable 2-Factor Authentication (MFA) if needed.
  • If you select Magic Link as the login method, the following options appear:
  • Enable sign-in from other IPs: When enabled, users can open the Magic Link from a different IP address than the one from which it was requested.
  • Enable sign-in from other devices: When enabled, users can open the Magic Link on a different device than the one used to request it.



• Click on Save. Policies will be created for all the selected groups.
• You will see the policy listed once it’s successfully added.



• You can go to the Advanced tab to change other settings, such as the expiry time for Access, JWT, and Refresh tokens.
1. Access Token Expiry: For how long the provided access token should be valid from creation. [In Hours] A new access token has to be generated after the expiry.
2. JWT Token Expiry: For how long the generated JWT token should be valid. [ In Hours ]
3. Refresh Token Expiry:For how long the generated refresh token should be valid. [In Days] You will have to generate a new refresh token after the mentioned no. of days.
4. Enable Shared Identity: This feature lets you control whether a specific application can be accessed by shared user or not.



• Switch to the Login options tab.

  Primary Identity Provider	Select the default ID source from the dropdown for the application. If not selected, users will see the default login screen and can choose their own IDP. [Choose miniOrange in this case.]
  SSO FLows	Select the desired SSO flow from the dropdown, such as miniOrange as IDP, miniOrange as Broker, or miniOrange as Broker with Discovery Flow.
  Show on Enduser Dashboard	Enable this option if you want to show this app in the end-user dashboard.
  Force Authentication	If you enable this option, users will have to log in every time, even if their session already exists.
  Allowed Logout URIs	Click the Allowed Logout URIs link to add a list of post-logout redirect URIs. Users will be redirected to one of these URIs after a successful logout from miniOrange.
  Single Logout Enabled	Enable this option to send logout requests to other applications when logging out from this app.
  Sign in URL	You can include user attributes in the sign-in URL using placeholders like {{username}}, {{primaryEmail}}, {{customAttribute1}}, etc. These placeholders will be dynamically replaced with the actual user values during the IdP-initiated SSO flow. You can generate url using following attributes: username, primaryEmail, alternateEmail, fname, lname, primaryPhone and customAttribute1. The url could be like this login.com/{{username}}/?primaryEmail={{primaryEmail}} Query Parameter Format: https://<sso-url>>?username={{username}} https://<sso-url>>?username={{username}}&email={{primaryEmail}} Path Parameter Format: https://<sso-url>>/{{customAttribute1}}/{{customAttribute2}}/?username={{username}}

• Getting Required App Details / Updating App Information:
• You can edit Application by using the following steps:
• Go to the Apps.
• From the list of configured apps, locate the app you created. Click the ( ⋮ ) icon next to the app and select the Edit option.



• Click the OAuth Endpoints section in Actions menu for your app to get the Authorization, Token and User Info Endpoints.




OAuth Endpoints:

Authorization Endpoint:	https://login.xecurify.com/moas/idp/openidsso (Note: Use this endpoint only if you want to use miniorange as oauth identity server.) https://login.xecurify.com/moas/broker/login/oauth/260174 (Note: Use this endpoint only if you are configuring any Identity Provider in Identity Providers Menu and not using miniorange as IDP.)
Token Endpoint:	https://login.xecurify.com/moas/rest/oauth/token
User Info Endpoint:	https://login.xecurify.com/moas/rest/oauth/getuserinfo
Introspection Endpoint:	https://login.xecurify.com/moas/rest/oauth/introspect
Device Authorization Endpoint	https://<your-company-name>.xecurify.com/moas/rest/oauth/devicecode/authorize This endpoint is used to initiate the OAuth 2.0 Device Authorization Grant flow for devices or applications with limited input capabilities or no browser. This endpoint takes the following parameters :
Revoke Endpoint:	https://login.xecurify.com/moas/rest/oauth/revoke
OpenID Single Logout Endpoint:	https://login.xecurify.com/moas/idp/oidc/logout?post_logout_redirect_uri=






OAuth Scopes

email :	View email address of the user
profile :	View profile attributes of the user account
openid :	Retrieve JWT token for OpenID Connect




• Click on Save.

2. Configure SSO in Qlik Cloud

• Login to Qlik Cloud as admin account.
• Go to Launcher Menu → Management Console.



• Click on Settings.



• Click on Identity provider → Create new.



• In Create identity provider configuration provide the required details:

Type	Interactive
Provider	Generic
Description (optional)	Write the description about your application




• In Application credentials click on checkbox to enable Manual Configuration and provide the required details in step 1.



• Now you will get the "Client ID", "Client Secret" from miniOrange console and paste it in your Qlik Cloud configuration from step 1.





• Click on Create button.

Validation Steps:

• In Management Console → Identity provider.
• In the table, to the far right, click on → Validate.



• Enable the checkbox of I have validated the above data and click on Confirm.



• In Promote user to tenant admin click on Continue.



• To activte IdP click on Activate button.



• After successful activation, you will get redirected to the below screen.



• Click on Close.
• To check the status is active in below screen.

3. Test Qlik Cloud SSO Configuration

• Go to https://{Your-Qlik-Cloud-Domain} and sign in/login.
• You will get a login window of Qlik Cloud and click on Sign in with SSO link.



• Enter your Hostname click on Submit button and you will be redirected to miniOrange Credential Section.



• Enter your miniOrange Credentials.



• You can see you have successfully implemented Single Sign-On for Qlik Cloud with miniOrange as your OAuth Server.

4. Configure Your User Directory (Optional)

miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Microsoft Entra ID, 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.

• Setup miniOrange as IDP
• Setup AD as User Directory
• Setup External IDP

• To add your users in miniOrange there are 2 ways:
• Create User in miniOrange
• Bulk Upload Users

1. Create User in miniOrange

• Click on Users >> User List >> 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. 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.

• 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 AD/LDAP Display Name and 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.

Import Password Policy from AD

• If you want to import your Active Directory password policy into miniOrange, 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.

miniOrange integrates with various external user sources such as directories, identity providers, and etc.

• Okta
• ADFS
• Ping
• AWS Cognito
• Many more

Not able to find your IdP or Need help setting it up?

Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

5. Adaptive Authentication with Qlik Cloud [This will be released soon]

Adaptive Authentication for Qlik Cloud 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 Qlik Cloud 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 :

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



• 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.
• Select Action for Behavior Change, choose the appropriate Action and Challenge Type for the user from that section.




Action for behavior Change Options :




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.




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 many more.
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.



• Click on Next to continue.

B. Restricting access to Qlik Cloud 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 :

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



• Click on the Dropdown option to expand the Device Based Access Restriction section to configure device-based access controls.



• Turn on the Enable Device Configuration toggle.



• Configure either Agentless Device Restriction or Agent-Based Device Restriction based on your organization's requirements.
• Agentless Device Restriction: Verifies and manages trusted devices without requiring any software or agent installation on the endpoint. It uses browser and device-based identification methods to evaluate device trust and enforce access policies during authentication.
• Agent-Based Device Restriction: Provides enhanced device trust verification by using a lightweight agent installed on managed devices. It enables advanced device validation and risk-based access control to ensure that only trusted devices can access protected resources.



• Click here to get more information about Device Based Restriction.
• Once the changes are made, click on Next.
• Under Action for Behaviour Change, select the appropriate action and challenge type for the policy.



• Click on Next to continue.

C. Restricting access to Qlik Cloud 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 :

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



• Click on the Dropdown to expand the Location Based Access Restriction section to configure location-based access rules.



• Select Register Location if User Completes Challenge to automatically register a user's location after successful challenge verification.
• Click on Add Location.



• In the Search Location field, enter the location name and select the appropriate location from the search results.
• Specify the radius around the selected location and choose the distance unit (KM or Miles). This will be the total area in and around the location we have configured using the Latitude and Longitude points.
• For each configured location, select whether access should be Allowed or Denied.



• You can click on the Add Location button to add more than one location and then follow steps 2-4 as mentioned above.
• Once the changes are made, click on Next.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.



• Click on Next to continue.

D. Restricting access to Qlik Cloud 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 :

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



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



• Enter the Login Window Buffer Time (Minutes) to allow a grace period before the start time and after the end time of the configured login window. If no value is specified, the default buffer time of 0 minutes is applied.
• Click Add Time to create a time-based access rule.



• Select the required Timezone, configure the Start Time and End Time and choose the applicable days.
• For each time-based rule, select whether access should be Allowed or Denied.



• Click on the Add Time to add more than one timezones.
• Once the changes are made, click on Next.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.



• Click on Next to continue.

E. Email Alerts and Custom Email Message

This section handles the notifications and alerts related to Adaptive Access Policy. 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.

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.




• Click on Create Policy.

G. Add Adaptive Authentication policy to Qlik Cloud

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



• Set your policy in the Policy Name and select Password as First Factor.



• Enable Adaptive Authentication on Edit Login Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step.
• Apply Restrictions Using: Configure how multiple adaptive authentication restrictions should be evaluated during user login.
  • AND: All enabled restrictions must be successfully satisfied for the login attempt to be allowed.
  • OR: At least one enabled restriction must be successfully satisfied for the login attempt to be allowed.



• Adaptive Authentication Restrictions: Configure additional login restrictions and verification conditions to strengthen account security and control user access based on contextual risk factors.
  • IP Restriction: Restrict login access to specific IP addresses or IP ranges for enhanced security.
  • Device Restriction: Allow login access only from trusted or pre-authorized devices.
  • Location Restriction: Control user login access based on geographic location.
  • Time Restriction: Restrict user login access to specific days or time periods.
  • Force MFA On Each Login Attempt: Require users to complete MFA verification during every login attempt regardless of device or session state.

How to add a trusted Device

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

External References

• What is Single Sign-On (SSO)?
• Configure Qlik Cloud SSO
• Know more about cloud SSO
• Explore Other Integrations