[Solved] Custom ISharedDataSourceResolver no longer works in v19.2.25.813

[Robin]

Based on our issue from 2 years ago, we implemented ISharedDataSourceResolver as a fix: https://www.telerik.com/forums/pass-user-claimsprincipal-from-reportscontroller-to-webservice-datasource-controller

    public class CustomSharedDataSourceResolver : Telerik.Reporting.Processing.Data.ISharedDataSourceResolver
    {
        /// <summary>
        /// Resolves and returns a DataSource instance from the provided <paramref name="sharedDataSourcePath"/> parameter.
        /// </summary>
        /// <param name="sharedDataSourcePath">The value of the Path property obtained from the report definition. Might be relative or absolute.</param>
        /// <returns></returns>
        public DataSource Resolve(string sharedDataSourcePath)
        {
            ValidateConfiguration();

            var absolutePathToSharedDataSourceDefinition =
                GetExistingFilePath(Configuration.Instance.ReportsPath, sharedDataSourcePath)
                ?? GetExistingFilePath(Configuration.Instance.SharedDataSourcesPath, sharedDataSourcePath);

[...]

It is registered in our Appsettings.json:

{
  "ConnectionStrings": {[...]},
  "AllowedHosts": "*",
  "AzureStorageBlobConfig": {[...]},
  "Logging": {[...]},
  "TelerikReporting": {
    "Processing": {
      "SharedDataSourceResolver": {
        "Provider": "custom",
        "Parameters": [
          {
            "Name": "typename",
            "Value": "TgsFlow.Plugin.Reporting.TelerikReporting.Utilities.CustomSharedDataSourceResolver, TgsFlow.Plugin.Reporting.TelerikReporting"
          }
        ]
      }
    }
  }
}

If I put a breakpoint on Resolve(), this breakpoint is hit on version 18.2.24.806 of Telerik.Reporting.Services.AspNetCore and Telerik.WebReportDesigner.Services. But if I upgrade those dependencies to 19.2.25.813 the breakpoint is no longer hit and the previously discussed fix no longer works.

[Petar]

Hi Robin,

Thank you for sharing your `appsettings.json` file.

Everything in the configuration looks correct to me. To double-check, I tried to reproduce the issue on my end using Reporting version `19.2.25.813` with the following settings:

{
  "TelerikReporting": {
    "Processing": {
      "SharedDataSourceResolver": {
        "Provider": "custom",
        "Parameters": [
          {
            "Name": "typename",
            "Value": "WebApplication1.Controllers.CustomSharedDataSourceResolver, WebApplication1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"
          }
        ]
      }
    }
  },
 "ConnectionStrings": {
   "Telerik.Reporting.Examples.CSharp.Properties.Settings.TelerikConnectionString": {
     "connectionString": "Data Source=.\\SQLEXPRESS;Initial Catalog=AdventureWorks;Integrated Security=true",
     "providerName": "System.Data.SqlClient"
   }
 }
}

However, with this setup, the breakpoint I placed inside the `Resolve` method was hit as expected (I returned `null` for the demo):

That said, could it be that the resolver type in question is part of an external assembly (not hosted within the REST service project itself)? In the latest versions, we have introduced a mechanism that prevents external assemblies from being automatically resolved by the report engine for security reasons, unless they are explicitly registered. If the resolver is indeed located in an external assembly, I recommend registering it in your `appsettings.json` through the `assemblyReferences` element.

If you need further assistance with this matter, it would be very helpful if you could enable a trace listener in the ASP.NET Core application and share the generated log file so that I can review it and spot any potential discrepancies. For more information on how to do this, please check Troubleshooting Reporting Implementation in ASP.NET Core Application.

Thank you, and I am looking forward to your reply!

Regards,
Petar
Progress Telerik