My experience is exactly what is described in this thread:
I have a remove server with a password protected report
It works if I do not check the UseProxy box. When the page loads, a box pops up and asks you to log in. When you do the report displays fine.
When I try to pass the password to display the report using the handler, the page its self works, but the assets of the Report viewer control don't load:
Why aren't they working though? What is the server response? What is the difference in the URL between UseProxy=true and UseProxy=false. We can't really help with troubleshooting as we cannot reproduce such an issue at our side.
Yes, but (because it was not in your example), I would need the [REPORT_PATH]properly put in:
http://[YOUR_SERVER]/ReportServer/Pages/ReportViewer.aspx?%2f[REPORT_PATH]%2f[YOUR_REPORT]&rs:Command=Render
Also, the code is currently writing:
https://[YOUR_SERVER]/Reports/Pages/ReportViewer.aspx?%2freports%2fFYIS_Transcipt&rs%3aCommand=Render&rs%3aEmbed=true
So it is putting in the [REPORT_PATH] properly, but going to:
https://[YOUR_SERVER]/Reports
not the proper:
https://[YOUR_SERVER]/Reportserver
My biggest fear is that even if I downgrade my SSRS and find a way to fix it to work for versions prior to 2017 it might stop working for newer versions of the SQL Server Reporting Services.
http://[myserver]/Reportserver/Pages/ReportViewer.aspx?%2fTrentReports/[myreport]&rs:Command=Render&rs:Embed=true
in browser works fine after authentication
Iβm unable to reproduce the issue and that is why I cannot tell whatβs causing it. The code of controller is part of the application provided for free and can be debugged.
@enchev I got access to a 2017 SSRS that is the exact same version of @ThomasS and my screen looks exactly like his. I zipped up the project and sent it to you as a private message. Hopefully that will help.