I have an application that uses Microsoft Entra ID authentication. After signing in, users can click a link that redirects them to Report Server for .NET, which is also configured to use Microsoft Entra ID authentication. However, users are not automatically signed in to Report Server after the redirect; instead, they are presented with the login page and must manually click the Microsoft Entra ID sign-in button to complete a separate authentication flow.

Please consider addressing this.

I need a way to hide the parameters in the URL, like Microsoft's SSRS uses an internal parameter that isn't passed in the URL.

Internal parameters are ideal for anchoring global variables (like UserID) within the report logic to filter data securely. Because the parameter is internal, a user cannot manipulate the URL to spoof another user's ID and view restricted data.

We are using the .NET Framework version of the Report Server. We have multiple reports that rely on multi-value report parameters. When we preview them separately, they render correctly. However, when we create scheduled tasks that rely on those reports, the parameter values we choose during the creation are not preserved, and the reports render incorrectly. Please consider resolving this issue.

Currently, the report parameters that are hidden appear in the modal when creating a new scheduled task and are editable.

I want to make them readonly by default for non-admin users, and perhaps a setting can be exposed in the configuration to control whether they should be editable or not.

I am using the Standalone Report Designer to connect to the Report Server for .NET. However, in the .NET version, I see an error "The JSON value could not be converted to System.Data.DataTable.") when opening the query designer or when attempting to use the preview functionality at the last step of the SqlDataSource wizard.

In the .NET Framework version of the Standalone Report Designer the wizard itself works as expected, but the Data Explorer does not show the available fields and I have to enter them manually.

Currently, the Shape item in the Web Report Designer exposes a smaller set of predefined shapes than the Standalone/Visual Studio designers.

For example, the Square type is not available in the Web Report Designer, and I have to configure it manually through the Shape item settings.

We've recently deployed a new infrastructure with multiple instances running Telerik Report Servers behind a load balancer.

In this new structure, we noticed a new intermittent bug when rendering some reports using the HTML5 report viewer, which is breaking some of our images included in PictureBox controls due to 400 Bad Request errors.

Upon further inspection, it seems the error happens because one of the instances is returning the following error instead of loading the image, hence the intermittency.

Provided document Id has expired. Please refresh your browser to generate a new one.

Please provide support for the FirebirdSql.Data.FirebirdClient, so that I can connect to my Firebird database.

Currently, I have to use the Firebird ODBC driver instead.

I am setting up a scheduled task with reports with WebServiceDataSource on the Telerik Report Server for .NET.  When I try run the scheduled tasks, I get the following error message when the data source contains JsonPath:

Could not load file or assembly 'JsonPath.Net, Version=2.0.0.0, Culture=neutral, PublicKeyToken=17ed63f672b0e278'. The system cannot find the file specified.

When there is no JsonPath in the WebServiceDataSource, the error is as follows:

Could not load file or assembly 'System.Text.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.

The Report Server is localizable. However, its viewer is not.

The localization of the viewer requires adding a new JavaScript file with the translation and referencing it in the CSHTML template of the Preview, which would be reset upon the Report Server upgrade.

It would be great if the localization of the Report Server Viewers became part of the configuration, allowing them to be preserved between upgrades.

Current Behavior

Telerik Report Server currently limits authentication to a single federation provider. Organizations requiring multiple identity providers must implement a custom authentication provider as a workaround.

Requested Enhancement

Allow configuration of multiple federation providers simultaneously within the Report Server administration interface, enabling users to authenticate via any configured IdP without custom development.

Use Case

• Organizations with multiple Azure AD/Entra ID tenants (e.g., separate tenants for different business units, subsidiaries, or during M&A transitions)
• Hybrid environments requiring both corporate IdP and partner/vendor IdP access
• Migration scenarios where legacy and new identity providers must coexist temporarily
• Multi-client SaaS deployments where each client uses their own identity provider

Proposed Implementation

• Admin UI to add/remove multiple SAML 2.0, OpenID Connect, or WS-Federation providers
• Provider selection presented at login (dropdown or separate buttons per IdP). Optional as could just as well aut select based on login.

Business Impact

The current single-provider limitation forces organizations into complex custom provider implementations, increasing maintenance burden and potential security risks. Native multi-provider support would reduce implementation complexity and align with modern enterprise identity management requirements.

Provide an official and supported migration path from the Telerik Report Server built on .NET Framework to the newer .NET-based Report Server, allowing reuse of existing storage and configuration.

Organizations running long-lived Telerik Report Server installations want to adopt the newer .NET version for performance, longevity, and platform alignment, without rebuilding their entire environment.
Lack of migration support is currently a blocker for adoption and increases operational costs.

Suggested Solutions

• A migration tool or script that converts credential storage to the new hashing algorithm

• A supported upgrade path that forces password resets but preserves users and roles

The Report Server is localizable. However, its viewer is not.

The viewer cannot be customized either. For example, if you want to make the default View mode PrintPreview.

The above require changes in the CSHTML template of the Preview, which would be reset upon the Report Server upgrade.

It would be great if the customization and localization of the Report Server Viewers became part of the configuration, allowing them to be preserved between upgrades.