HTML5 Report Viewer - Service URL Attach Cookie

[Joshua]

When using the HTML5 ReportViewer, you can add a service URL for the REST Service.  Is it possible to attach a cookie to the call back to the service?  Our REST Service is in a different App Service so the authentication cookie needs to be passed along.  There is an authentication parameter but doesn't appear to work the way I need it to.

[Stef]

Hello Joshua,

Please check the following stackoverflow discussion - Why is jquery's .ajax() method not sending my session cookie?. The discussion elaborates why cookies are not sent between different domains and how you can workaround the security settings.

In general, the HTML5 Viewer makes AJAX requests to the Reporting REST Service. We provide mechanism for sending custom header information - authenticationToken attribute of the HTML5 Viewer. You can override the Reporting REST Services methods (ReportsControllerBase methods) to handle the security information by adding attributes and custom code.

Regards,
Stef
Telerik by Progress

[Joshua]

Are you are telling me that I can either...

A.  Change my authentication Logic to use this bearer token you speak of instead of using my normal cookie method?

B.  Edit your java script files to implement a hack to the Ajax call that the report viewer makes in the ways described in the link you linked to?

[Stef]

Hi Joshua,

You can create a token and use it with the HTML% Viewer that makes AJAX requests to the Reporting REST Service (it is a WebAPI controlleR).

You can pass the token through the viewer's authenticationToken, no need to change the viewer's script.

Then you can add authorization attributes on the ReportsControllerBase controller's class and any method in it (methods can be overridden).

Regards,
Stef
Telerik by Progress

[Joshua]

I found I was able to make it work by adding the following code in a common place, 

$.ajaxSetup({ xhrFields: { withCredentials: true}});

This caused ajax to pass the cookie.  Now, the initial call to the reports service works and doesn't give the authorization error, but then it tries to make a second HTTP OPTIONS call to /services/reports/api/reports/clients/094002-f5f9/parameters and it gives a 404 not found error.  Still working on this one.

[Joshua]

I was able (as mentioned in my other comment) to get the credentials passed through.  Now the first request to service/reports/api/reports/clients works fine and returns a 200 Status Code and returns a client id {in my latest test the client id is 071748-9ec9}.  Then it makes a second request to service/reports/api/reports/clients/071748-9ec9/parameters, it also has created a folder on the server in a temp directory matching the client id.  But this second call to the parameters gets a 404 not found status code.  Any thoughts as to why this would be occurring?

[Katia]

Hi Joshua,

What is the error message you receive in the viewer?

Check if the viewer's reportSource is configured correctly - How to: Set ReportSource for Report Viewers. Also, check the suggestions listed in this forum post.

Regards,
Katia
Progress Telerik