| Groups | Blog | Home |
sql server reporting services : VisualStudio 2005 Web ReportViewer Control
[quoted text, click to view]
"Andrew Teece" <enate@newsgroups.nospam> wrote in message news:uPCQ1ewXGHA.4184@TK2MSFTNGP03.phx.gbl > Just a little question.... Don't know about the SQL group but m.p.vb.g.d is the wrong group for Visual Studio 2005 questions; look for groups with "dotnet" in the name. This group is for VB 6.0 and earlier. VB.Net is Not.VB -- Reply to the group so all can participate VB.Net: "Fool me once..."
A SQL Server 2005 license is needed for every server that is running
Reporting Services. If all you have on your webfarm is the control in your web pages then no, you do not need the SQL Server 2005 license (note this is the server licencing I am talking about). If Reporting Services server is installed on your web farm then yes, you need the license. It sounds like in your case that the web farm has the control and it does not have the RS server installed. If so, then no additional licensing is required. I don't know about the second question. I do know that web services is used in the connection. I also know that a common issue with security has to do with double hop when using integrated security (which it sounds like you are). Don't confuse ip addressing issues with security domains. If you are using windows security (i.e. you are not doing your own forms based security) then you need to be using kerberos in order to get around the double hop problem. So, the more important question for you is, is this an intranet or internet application. If internet then you will need to be using Forms security. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Andrew Teece" <enate@newsgroups.nospam> wrote in message news:uPCQ1ewXGHA.4184@TK2MSFTNGP03.phx.gbl... > Just a little question.... > > From my understanding, the report viewer control sends the client machine > an iFrame that connects directly to the SQL Reporting server (at least > when using reports in SQL rather than local ones). > > So this means that we must have SQL Server 2005 licensed and installed on > our entire webfarm? > > Secondly, if the sql server 2005 is a DIFFERENT webserver, on a different > domain, or subdomain such as "reporting.webfarmurl.com", and the site is > running ssl, so our users are connected to https://www.webfarmurl.com will > IE let an iframe connect to another URL such as > http://reporting.webfarmurl.com or https://reporting.webfarmurl.com? > > > > Regards > > > > > Andrew >
Just a little question....
From my understanding, the report viewer control sends the client machine an iFrame that connects directly to the SQL Reporting server (at least when using reports in SQL rather than local ones). So this means that we must have SQL Server 2005 licensed and installed on our entire webfarm? Secondly, if the sql server 2005 is a DIFFERENT webserver, on a different domain, or subdomain such as "reporting.webfarmurl.com", and the site is running ssl, so our users are connected to https://www.webfarmurl.com will IE let an iframe connect to another URL such as http://reporting.webfarmurl.com or https://reporting.webfarmurl.com? Regards Andrew
We have developed our reporting solution based on Reporting Services 2005,
and our application has been deployed by our customer onto 5 servers, 3 front-end web servers and 2 back-end database servers (clustered). As they are not going to open up the SQL Servers to HTTP traffic, we believe that the solution is to install (and obviously license) SQL Server 2005, to put just the RS component of SQL05 onto the webservers. What we are looking into though, is putting SQL05 onto just one of the web servers, and using a second domain, outside of load balancing. However, the reports would still be called from our application on Domain A. So my security question is about a secure SSL site on Domain A showing an iFrame with the reports from Domain B. We are not using integrated security, we have implemented custom auth providers for the reports. This is an internet application. Regards Andrew Teece Senior Developer, eNate [quoted text, click to view] "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in message news:%23azoprwXGHA.3684@TK2MSFTNGP05.phx.gbl... >A SQL Server 2005 license is needed for every server that is running >Reporting Services. If all you have on your webfarm is the control in your >web pages then no, you do not need the SQL Server 2005 license (note this >is the server licencing I am talking about). If Reporting Services server >is installed on your web farm then yes, you need the license. > > It sounds like in your case that the web farm has the control and it does > not have the RS server installed. If so, then no additional licensing is > required. > > I don't know about the second question. I do know that web services is > used in the connection. I also know that a common issue with security has > to do with double hop when using integrated security (which it sounds like > you are). Don't confuse ip addressing issues with security domains. If you > are using windows security (i.e. you are not doing your own forms based > security) then you need to be using kerberos in order to get around the > double hop problem. > > So, the more important question for you is, is this an intranet or > internet application. If internet then you will need to be using Forms > security. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > > "Andrew Teece" <enate@newsgroups.nospam> wrote in message > news:uPCQ1ewXGHA.4184@TK2MSFTNGP03.phx.gbl... >> Just a little question.... >> >> From my understanding, the report viewer control sends the client machine >> an iFrame that connects directly to the SQL Reporting server (at least >> when using reports in SQL rather than local ones). >> >> So this means that we must have SQL Server 2005 licensed and installed on >> our entire webfarm? >> >> Secondly, if the sql server 2005 is a DIFFERENT webserver, on a different >> domain, or subdomain such as "reporting.webfarmurl.com", and the site is >> running ssl, so our users are connected to https://www.webfarmurl.com >> will IE let an iframe connect to another URL such as >> http://reporting.webfarmurl.com or https://reporting.webfarmurl.com? >> >> >> >> Regards >> >> >> >> >> Andrew >> > >
Hi Andrew,
As for the he resporting service's license, it just depend on the server-side service's SQLServer license, nothing related to reportViewer control. ReportViewer is just the component provided by Visual Studio and .net framework. Also, for iframe, when our SSL protected web page contains iframe point to unprotected http page, there will occur warning message at client-side browser: #PRB: Security Warning Message Occurs When You Browse to a Page That Contains an IFRAME Through SSL http://support.microsoft.com/kb/261188/en-us In addition, if you've implemented custom security extension for reportingservice which require user interactive operation(like forms authentication extension), those component which programmatically access reporting service will not work(the ReportViewer control is one of such components). Hope this also helps. Regards, Steven Cheng Microsoft Online Community Support ================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Get Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.)
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
January 2009
| home · blog · groups | Questions? Comments? Contact the dn |