Welcome to the Embedded Reporting feedback portal. We’re happy you’re here! If you have feedback on how to improve the Embedded Reporting, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Details:

1)      We have our own .Net Core controller that implements the Syncfusion IReportDesignerController interface.

2)      Methods in this controller are secured through the [Authorize] attribute.

3)      The JSON web token is passed from the Report Viewer component using the serviceAuthorizationToken property.


NOTE:  The Report Designer is using the JWT in nearly all the calls that it makes to the controller except for some calls to PostFormReportAction. 


A work around that I have discovered is to allow anonymous calls to this method in the controller:


        [AllowAnonymous]  // Workaround for download bug

        public object PostFormReportAction()

        {

            return ReportHelper.ProcessReport(null, this, _cache);

        }