Articles avec le tag :
Centre d'aide
Control Panel

How to deploy multiple portals using the Multitenancy feature?

Control Panelv.2.7 Control Panel changelog

Version 2.7

Release date: 04/25/2019


  • Added more fields mapped for the users loaded via LDAP: user photo, birthday, contacts, primary phone number;
  • Added the setting to autosync LDAP on schedule;
  • Added the possibility to give administrator rights to the user group at the portal via LDAP;
  • Updated the rules for LDAP users.

Version 2.5.1

Release date: 04/07/2018


  • Fixed the Server internal error error when using the groups enclosed inside each other in the AD (bug #37414).

Single Sign-on

  • Fixed the issue when the user data between the Service Provider and the portal was transferred via HTTP only, even when HTTPS was enabled.

Version 2.4.0

Release date: 01/13/2018

Single Sign-on

  • Fixed the Invalid ssoConfig error which occurred when the link to the IdP contained the question mark '?', e.g.: IdP Single Sign-On Endpoint URL:;
  • Fixed the Invalid authentication token error which prevented from adding a user to the portal using the AD FS, in case the + or - characters were present when sending the encrypted data.

Version 2.3.0

Release date: 12/15/2017


  • Added the changelog for Control Panel and link to it;
  • Fixed the bug when JWT parameters were not sent when updating Document Server(bug #36270);
  • Fixed the bug when Audit Trail heading was present at the login history page (bug #36026);
  • The current machine is now checked for being linked with the domain name for multiple portals.


  • Fixed the bug with the LDAP Domain not found error which occurred if the DN record had no DC records (the users with Sun/Oracle DS were affected); now if the LDAP domain could not be specified, the LDAP domain will acquire the unknown value or the ldap.domain value from the web.appsettings.config configuration file;
  • Fixed the bug with the Sizelimit Exceeded error when trying to get more than 1000 users from the Active Directory;
  • Increased the login speed with the Group Membership setting enabled;
  • Added additional logging;
  • Fixed the bug with LDAP operation hanging when using Mono v5.2.0 and older;
  • Fixed the bug with the error when trying to login using the email address entered in the fields different from the Mail Attribute;
  • Fixed the bug occurring in the enclosed groups, when the users were displayed not in all groups.

Version 2.2.0

Release date: 10/31/2017


  • Added the script launch when updating the document-server for the correct edited document saving.


  • Dramatically changed LDAP integration, migrated to the single library for the work with LDAP (Novell.Directory.Ldap.NETStandard, Nuget, MIT);
  • Login and email are now split into two separate fields;
  • Added the support for big data;
  • Increased the work speed via the LDAP protocol (the connection to the server and receiving the data is now made once per session, added the limits when only a certain number of results is necessary, fixed the slow login for bit data, removed the sorting out used to find the SID parameter);
  • Fixed the user re-creation issue;
  • Fixed the duplicate username issue;
  • Fixed the already existing email issue;
  • Replaced the LDAP user deletion with account deactivation (for further data migration and data safety);
  • Instead of re-creating a user with an unknown SID but an existing email the data is updated;
  • Added the attempt to save the correct UserName/Login in case a similar one is already taken on the portal.

Single Sign-on

  • Added the AD FS support;
  • Replaced the Single Sign-on link at the authorization page with the customizable button, added the button customization to the SSO setting of the Control Panel.

Version 2.1.0

Release date: 07/03/2017


  • Added the support of letsencrypt service for the domain certificate generation.

Single Sign-on

  • Added the new sso.auth service;
  • Added the new SSO settings page;
  • Added the support for Shibboleth.

Version 2.0.0

Release date: 05/25/2017


  • The Control Panel migrated from MVC to Node.js.

Version 1.6.0

Release date: 12/05/2016


  • Added LDAP synchronization for users and groups when saving the settings, after login and using the Sync button;
  • Changed email formation for LDAP users;
  • Fixed the problem of creation of users with invalid emails;
  • Fixed the problem of duplicate users;
  • Added icons and hints to the users in the list for the admin;
  • Blocked for editing the user profile fields imported using LDAP;
  • Added the real LDAP password saving to the database during login in case LDAP Auth is disabled, now the LDAP users will become common portal users when LDAP Auth is disabled;
  • Added new API Settings method - Sync LDAP;
  • Added new translations;
  • Bug fixes.

Version for Windows

  • Made changes at the Update page for the Control Panel for Windows;
  • Updates are performed using the downloaded installation packages for each module.
  • The current installed component version numbers are obtained via API request to the Community Server.
  • The new versions available for download are obtained via the request to the file, where all the latest component version numbers and links for their download are stored in the JSON format.


In case you have a large number of users, you might need a solution that allows to reduce licensing and infrastructure costs as well as simplify the software deployment and maintenance. Enterprise Edition provides you such a possibility. You can run several independent portals from a single Enterprise Edition installation instead of installing several application instances on separate servers.

For example, you can create individual portals for certain departments of your organization so that each portal contains own data and has some individual settings, but all the portals can be centrally updated and managed via Control Panel.

Using the Enterprise Edition Standard subscription you will be able to create two portals, in case you need more portals, you can select the Enterprise Edition Standard+ pricing plan which allows to create an unlimited number of portals.

Step 1. Set up your domain name

To use the multitenancy functionality, you need to have a registered domain name. In your domain DNS settings, create the following records:

  1. Create the A record that points your domain name to the IP address of the server where Enterprise Edition is installed.
  2. Create the wildcard A record specifying the asterisk "*" as a name to enable subdomains.

Your settings should look something like this:

Set up your domain name Set up your domain name

Step 2. Configure the current portal

To access Control Panel, sign in to your portal and click the 'Control Panel' link on the Start Page. Alternatively, you can go to the portal 'Settings' and click the 'Control Panel' link on the left-side panel.

In the Control Panel, switch to the Multitenancy tab. Specify your domain name in the first entry field. Then enter any portal name you like in the second field (it must be at least 6 characters long) and click the CONNECT button.

Configure the current portal Configure the current portal

The portal start page will open in a new browser tab at the address.

If you wish to rename your portal later, you will be able to do that in the portal settings: Settings->Common->Customization. Go to the Portal Renaming section, specify a new portal name in the corresponding field and click Save.

Step 3. Create a new portal

At the Multitenancy tab of the Control Panel, click the NEW PORTAL button and specify a name for your second portal, then click OK to save it. If you have not unchecked the Visit this portal after creating option that is selected by default, you will be redirected to the new portal that is available at the address.

Create a new portal Create a new portal

The Portal Setup page will open in a new browser tab. Specify and confirm your password and optionally change the email to create the Administrator account. You will not need to upload the license file as it is applied to all the portals at once.

To configure some individual settings for the new portal, go to the Portal Settings. You can adjust Customization settings (portal language and time zone, welcome page settings, team template, color scheme), select the necessary Modules and Tools to use, specify Security settings and SMTP settings.

Step 4. Manage your portals

You can access Control Panel from each of the created portals. At the Multitenancy tab you can view the overall number of your created portals and the license information. If you want to upgrade your pricing plan, click the Pricing plan settings link to go to the Payments page.

All the created portal addresses are also displayed at the Multitenancy tab. You can navigate between them clicking the portal you want to go to.

Manage your portals Manage your portals
Warning We strongly recommend that you do not change the domain name if your portal contains data because this may cause unpredictable consequences.

If for some reasons you nevertheless decide to change the domain name, click the EDIT button in the Domain settings section. In a new window that opens, set a new domain name and click OK.

Manage your portals Manage your portals

After changing the domain name you might also need to reconfigure some settings. For example, if you have connected Jabber clients, you will need to specify the new domain name in the client settings.

Download Host on your own server Available for
Docker, Windows and Linux
Cela peut vous aider aussi :