security/cookies and which controls running on client/server
Posted: Fri Jul 27, 2012 8:56 am
Hi,
We got the following setup:
ws: plaintext auth secured ssl linux web server with images and data
rs: plaintext auth secured ssl windows reporting server
As a data source for reports on RS we use XML/XSL hosted and dynamically generated on WS. Currently we have to authenticate again though and were wondering how to get around it.
The workflow is:
1) WS: user clicks on link to open reporting on RS
2) RS: the reporting pages loads in ASP.NET
3) RS: via the URL we know the data the user wants to report on in this case page 343434
4) RS: we build the dictionary for Stimulsoft and use as a data source the RS server: https://ws/data/343434/xml,https://ws/data/343434/xsl
5) RS: we open a report, set the dictionary and tell the browser to render in the users browser
6) RS: Now Stimulsoft displays in users browser, loads the dictionary, tries to access the data
7) RS: Now the users browser has to authenticate again as the report runs from server RS but the data is on WS.
Question: How can we avoid that the user has to log in again please?
e.g. could we log in on the server and pass the cookie along to the client side?
Also along these lines what is the client /serer work flow for these controls please?
ASP.NET Reports Viewer with Ajax client-side: access data and render on server side and just display data in browser? e.g. WS data is accessed from server only
ASP.NET Reports Viewer with Flash client-side: access data and render on client side? e.g. WS data is accessed from client directly
ASP.NET Reports Designer with Flash client-side: access data and render on client side? e.g. WS data is accessed from client directly
Thanks a lot,
Patrick
We got the following setup:
ws: plaintext auth secured ssl linux web server with images and data
rs: plaintext auth secured ssl windows reporting server
As a data source for reports on RS we use XML/XSL hosted and dynamically generated on WS. Currently we have to authenticate again though and were wondering how to get around it.
The workflow is:
1) WS: user clicks on link to open reporting on RS
2) RS: the reporting pages loads in ASP.NET
3) RS: via the URL we know the data the user wants to report on in this case page 343434
4) RS: we build the dictionary for Stimulsoft and use as a data source the RS server: https://ws/data/343434/xml,https://ws/data/343434/xsl
5) RS: we open a report, set the dictionary and tell the browser to render in the users browser
6) RS: Now Stimulsoft displays in users browser, loads the dictionary, tries to access the data
7) RS: Now the users browser has to authenticate again as the report runs from server RS but the data is on WS.
Question: How can we avoid that the user has to log in again please?
e.g. could we log in on the server and pass the cookie along to the client side?
Also along these lines what is the client /serer work flow for these controls please?
ASP.NET Reports Viewer with Ajax client-side: access data and render on server side and just display data in browser? e.g. WS data is accessed from server only
ASP.NET Reports Viewer with Flash client-side: access data and render on client side? e.g. WS data is accessed from client directly
ASP.NET Reports Designer with Flash client-side: access data and render on client side? e.g. WS data is accessed from client directly
Thanks a lot,
Patrick