Unplanned
Last Updated: 28 Jan 2020 11:00 by ADMIN
ADMIN
Milen
Created on: 29 Nov 2017 09:57
Type: Feature Request
17
Add multitenancy support
As a user utilizing the Report Server product, I need to use a single instance of it to serve two or more completely separated divisions/clients so that they do not have access to each other's assets, so that I do not have to make two different deployments of the server and support them. See https://en.wikipedia.org/wiki/Multitenancy
5 comments
ADMIN
Todor
Posted on: 28 Jan 2020 11:00

Hi Espen,

The multitenancy feature is in our plans and will be implemented based on its priority. The task is not started yet.

I can suggest a workaround for your requirements though. You may set the ConnectionString through Bindings as explained in the Change Connection String dynamically through a report parameter KB article. Instead of Report Parameter, you may utilize User Function that takes as an argument the logged user - for example through the UserIdentity global object. The function should return the correct connection string based on the user. The approach with the user function is recommended as the Report Parameter values are included in the Url with the request for the report, which will be a security issue. Note that this approach won't work for Report Parameter AvailableValues SqlDataSource.

Regards,
Todor
Progress Telerik

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Espen
Posted on: 20 Jan 2020 13:50

Any news on this feature?

As Frank, we have a single page application. We currently deploy one solution for each customer, but are in the process of implementing multi tenancy. We are facing the choice between sharing database between multiple customers or having one database each, but common web services for the customers.

- If we go for separate databases, it looks like report management can become a major pain as we have to duplicate reports with custom connection string in each

- If we go for shared database, I fear that it will not be possible to let customers design their own reports as we cannot prevent them from seeing other customer's data.

Any advice on how to solve this with Telerik report server?

ADMIN
Milen
Posted on: 18 Feb 2019 17:57
Hello Frank,

This actually looks like a different feature request. As I get it you would like to have one and the same set of reports for each user, without copying them. Just have a different DB connection for each client.
Multi-tenancy on the other side is like gmail. Each client has its own set of assets (like reports, emails, does not matter) and does not share any assets with other users.

Please elaborate, so that together we decide if a separate feature request should be created.

Regards,
Milen
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
ADMIN
Silviya
Posted on: 15 Feb 2019 19:04
Hello Frank,

It is definitely in our plans to add multi-tenancy feature. Thank you for your input! 

Best Regards,
Silviya
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Frank
Posted on: 15 Feb 2019 09:28

Yes exactly.

We are developing a multi-client SPA in which each customer receives their own database.
So nobody can see each other's data.

In our project, we want to integrate the Report Viewer, which should display a standard set of reports from the report server.
Each client receives an account on the report server.

Depending on the authenticated user, only the data connection for the reoprt must then be dynamically adapted to his DB.

Currently, this is only possible by creating a category (with appropriate rights) and a data connection to its database for each client. Then a series of reports for him purely copied. And in these reports, the data connection adapts.

The administration of many customers is then very cumbersome and error-prone.