Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hello Gurus,
We are accessing our reports from another application using reverse proxy which using YARP. We can open the report but when open the report we got a error prompt from report server, clicking OK then continue. Do you have an idea what is wrong?
Adding basic authentication information on request header.
var base64EncodedAuthenticationString = Convert.ToBase64String(
System.Text.ASCIIEncoding.UTF8.GetBytes(user.WindowsUsername + ":" + user.WindowsPassword));
context.Request.Headers.Append("Authorization", "Basic " + base64EncodedAuthenticationString);
await _next.Invoke(context);
Here is the yarp config
"ReverseProxy": {
"Routes": {
"route1": {
"ClusterId": "cluster1",
"Match": {
"Path": "{**catch-all}"
}
}
},
"Clusters": {
"cluster1": {
"Destinations": {
"destination1": {
"Address": "*********"
}
}
}
}
}
Solved! Go to Solution.
Thank you d_gosbell
Hi, @pelitahmet
I think you should configure the reverse proxy as instructed in the official documentation. Your problem appears on the report authentication page, which means that you are accessing the report through a reverse proxy server
server server failed to pass or an incorrect authorization was passed to the report server.
Here are the documents you should refer to and learn:
Creating the Web Service Proxy - SQL Server Reporting Services (SSRS) | Microsoft Learn
Alternatively, you can refer to the existing GitHub open source project, which uses yarp to proxy the report server:
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you d_gosbell
Hi, @pelitahmet
I think you should configure the reverse proxy as instructed in the official documentation. Your problem appears on the report authentication page, which means that you are accessing the report through a reverse proxy server
server server failed to pass or an incorrect authorization was passed to the report server.
Here are the documents you should refer to and learn:
Creating the Web Service Proxy - SQL Server Reporting Services (SSRS) | Microsoft Learn
Alternatively, you can refer to the existing GitHub open source project, which uses yarp to proxy the report server:
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Have you configured Basic Authentication? Configure Basic authentication on the report server - SQL Server Reporting Services (SSRS) | Microso...
By default Report Server will use integrated NTLM auth.