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.
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.
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.
Background: Our report server database undergoes maintenance every weekend. As part of this, the report server DB is taken down without stopping the Telerik service. When the DB comes back online the reporting service doesn't recognize the re-instated DB and doesn't send out reports. Reply from Telerik Support: My assumption is that the Report Server has hanged due to an error when the Storage was not available. The service has probably remained in this undefined state even after re-starting the database. Note that the Storage is a required resource, hence the service cannot work without it. We have logged the current behavior of Report Server with respect to its Storage database for improvement in our system. Feature request: It would be nice to get an alert/email to the Report server admins that the Report Server DB/Storage is unavailable.
As a developer integrating the the Report Server with my solution, I would like to be able to apply a fully customizable Kendo theme to the Report Server server app so that it can blend fully with my applications.
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
I extensively use sub reports with drill-down, drill-through actions and to fetch data, into the main report, extracted from different datasets based on a set of certain parameters. When I upload these reports to the server, I assign main and sub reports to two separate categories 'Main' and 'SubR' so that I can manage reports and users' permissions accordingly. Currently, it is not possible to 'hide' the reports under 'SubR' category for a user so that all the sub reports are hidden from view, leaving visibility of main reports only for that user. I tried by restricting user's access to the category 'SubR' so that sub reports are not visible in the list and avoid confusion from user's perspective. But when I restrict user's access to the category 'SubR', all the main reports that contain sub reports do not run correctly and start displaying 'unable to access subreport1...' error. The same error comes up if I have included a report in the main report, accessible by drill-through action. I would like to request for a functionality to 'Hide / Display' reports in conjunction with 'Read' access to the reports. This will provide further granularity to the way the reports can be made accessible and still be hidden from view.
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.