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
Reports with resources for different languages should be rendered with the language resources and client culture.
We have standardized the usage of Central Identity System across applications using OAuth and OpenId connect based https://identityserver.io/.
As a report editor, I want to authenticate to report server frontend using IdentityServer.io Single sign on.
As IdentityServer is .net server core based, we would like ReportServer also .net core based to support non-windows hosting scenario.
In order to provide better data-driven subscriptions implementation, the subscribers of a Scheduled Task or Data Alert should be modified dynamically. Currently they are a static list of emails, which is not convenient when a report must be sent to a whole group of users in an organization, because the group members can constantly fluctuate. Report Server should provide the option to declare an external data retrieval service in the ST/DA subscribers list. This service could be a REST API endpoint or a file path that will return the list with the subscriber emails.
After changing the culture settings on the server machine to EN-GB (which should display the date in dd/MM/yyyy format), the Preview of the report parameters still shows the date format as default, in US format (MM/dd/yyyy).
However, I would not expect to have modified the code to fix this, it should be a configurable option and/or take local server formatting.
We get all data from a REST API with an OAuth 2.0 token-based protection. Is there a way to implement the login once and use the token for each data source? Right now, if I have multiple data sources in the same report, each one has the 2-step Authentication Settings and does its own login to the REST API.
Currently, the only way to integrate with Active Directory is to use Federation Services. We do not have a Federation Server nor do we require one. It would be great to add the LDAP information and be able to authenticate with AD. While larger organizations use ADFS and its required for Azure, for small networks and organizations, ADFS is overkill for trying to achieve SSO.