Report Viewer/Authentication

Hello,
We are trying to avoid the login pop-up when using the report viewer control
from an internet facing solution. Sorry it is long, but here is the scenario.
ServerA (the webserver, windows 2000 server, v1.1 framework) is serving a
legacy ASP application that we have added an ASP.NET page that uses the
report viewer control to connect to ServerB.
ServerB (the report server, windows 2003 server SP1, RS Standard Edition
SP2) there is a public IP that is Nat's to a local IP of ServerB. This is
what the report viewer control uses from ServerA. ServerB has a local user
that has full access to the reports that need to be delivered.
When you first try to access the report server (ServerB) from the internet
it prompts for a username and password. Once the local user's credentials
from ServerB have been entered we are able to view all reports until the
browser is closed. We have RS 2000 Standard Edition so there is no option for
a custom security extension.
Is there anyway that we can avoid forcing the web users to type in the
username and password that was setup on ServerB? I have tried everything I
can think of and have had no success. There are many security issues with
making that RS login public using URL access and even more security issues by
making the report server allow anonymous access. I need a solution!
Any help would be greatly appreciated.
Thanks in advance!how your users are authenticated on the serverA?
(form authentication or basic authentication?)
The reportviewer webcontrol is a ASP.Net 2.0 control.
do you use another version?
the .Net 2 version is great, because this version will do what you want to
do!
in .Net 1.1...
To solve your issue, you have to intercept and process the reports using
your own webpages and not authorize the user to access your report server
directly.
(the user must go through your own pages, so you control which credential
will be used to access reportserver instead of prompting the user)
"Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
> Hello,
> We are trying to avoid the login pop-up when using the report viewer
> control
> from an internet facing solution. Sorry it is long, but here is the
> scenario.
> ServerA (the webserver, windows 2000 server, v1.1 framework) is serving a
> legacy ASP application that we have added an ASP.NET page that uses the
> report viewer control to connect to ServerB.
> ServerB (the report server, windows 2003 server SP1, RS Standard Edition
> SP2) there is a public IP that is Nat's to a local IP of ServerB. This is
> what the report viewer control uses from ServerA. ServerB has a local
> user
> that has full access to the reports that need to be delivered.
> When you first try to access the report server (ServerB) from the internet
> it prompts for a username and password. Once the local user's credentials
> from ServerB have been entered we are able to view all reports until the
> browser is closed. We have RS 2000 Standard Edition so there is no option
> for
> a custom security extension.
> Is there anyway that we can avoid forcing the web users to type in the
> username and password that was setup on ServerB? I have tried everything
> I
> can think of and have had no success. There are many security issues with
> making that RS login public using URL access and even more security issues
> by
> making the report server allow anonymous access. I need a solution!
> Any help would be greatly appreciated.
> Thanks in advance!|||Users on serverA are authenticated with a custom SQL login from the ASP
pages. The entire site on serverA is classic ASP. We are trying to add the
ASPX page with the report viewer control. We are able to determine if the
users are authenticated once they hit the ASPX/Report Viewer page.
We are using the 1.1 version of the report viewer control that came with SP1
or SP2 for RS 2000.
Once the web user accesses our ASPX page with the report viewer control how
do we set the credentials that access the report server via URL? That is
were everything stops working as planned and the standard login pop-up shows.
You can type the credentials of the user we want them to access with and
everything works fine from that point forward. But we want to set the
credentials in the code-behind of the page and not make the credentials
publicly available.
Any help you could provide to set the credentials that will be used by the
report viewer control would be greatly appreciated. I have poured many hours
into these reports and the integration with the classic ASP site. The
reports use custom assemblies to dynamically build the SQL statements, etc.
but now I can't get internet access to them using the report viewer without
manually typing in the credentials!
Thank you very much.
"Jéjé" wrote:
> how your users are authenticated on the serverA?
> (form authentication or basic authentication?)
> The reportviewer webcontrol is a ASP.Net 2.0 control.
> do you use another version?
> the .Net 2 version is great, because this version will do what you want to
> do!
> in .Net 1.1...
> To solve your issue, you have to intercept and process the reports using
> your own webpages and not authorize the user to access your report server
> directly.
> (the user must go through your own pages, so you control which credential
> will be used to access reportserver instead of prompting the user)
>
> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
> news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
> > Hello,
> >
> > We are trying to avoid the login pop-up when using the report viewer
> > control
> > from an internet facing solution. Sorry it is long, but here is the
> > scenario.
> >
> > ServerA (the webserver, windows 2000 server, v1.1 framework) is serving a
> > legacy ASP application that we have added an ASP.NET page that uses the
> > report viewer control to connect to ServerB.
> >
> > ServerB (the report server, windows 2003 server SP1, RS Standard Edition
> > SP2) there is a public IP that is Nat's to a local IP of ServerB. This is
> > what the report viewer control uses from ServerA. ServerB has a local
> > user
> > that has full access to the reports that need to be delivered.
> >
> > When you first try to access the report server (ServerB) from the internet
> > it prompts for a username and password. Once the local user's credentials
> > from ServerB have been entered we are able to view all reports until the
> > browser is closed. We have RS 2000 Standard Edition so there is no option
> > for
> > a custom security extension.
> >
> > Is there anyway that we can avoid forcing the web users to type in the
> > username and password that was setup on ServerB? I have tried everything
> > I
> > can think of and have had no success. There are many security issues with
> > making that RS login public using URL access and even more security issues
> > by
> > making the report server allow anonymous access. I need a solution!
> >
> > Any help would be greatly appreciated.
> >
> > Thanks in advance!
>
>|||this control use an IFrame to render the report.
this IFrame "redirect" the user to RS directly.
To override this issue you have to open your pages on the ServerA web site
and disallow the users to access the serverb directly.
To do this, you have to render the reports by yourself using your own ASPX
page(s) (you have to call the SOAP API and not use the URL access)
another way...
look at this reverse proxy tool:
http://www.saltypickle.com/Home/16
"Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
news:059772D9-D2AF-4725-A036-D8AB78B9CE04@.microsoft.com...
> Users on serverA are authenticated with a custom SQL login from the ASP
> pages. The entire site on serverA is classic ASP. We are trying to add
> the
> ASPX page with the report viewer control. We are able to determine if the
> users are authenticated once they hit the ASPX/Report Viewer page.
> We are using the 1.1 version of the report viewer control that came with
> SP1
> or SP2 for RS 2000.
> Once the web user accesses our ASPX page with the report viewer control
> how
> do we set the credentials that access the report server via URL? That is
> were everything stops working as planned and the standard login pop-up
> shows.
> You can type the credentials of the user we want them to access with and
> everything works fine from that point forward. But we want to set the
> credentials in the code-behind of the page and not make the credentials
> publicly available.
> Any help you could provide to set the credentials that will be used by the
> report viewer control would be greatly appreciated. I have poured many
> hours
> into these reports and the integration with the classic ASP site. The
> reports use custom assemblies to dynamically build the SQL statements,
> etc.
> but now I can't get internet access to them using the report viewer
> without
> manually typing in the credentials!
> Thank you very much.
>
> "Jéjé" wrote:
>> how your users are authenticated on the serverA?
>> (form authentication or basic authentication?)
>> The reportviewer webcontrol is a ASP.Net 2.0 control.
>> do you use another version?
>> the .Net 2 version is great, because this version will do what you want
>> to
>> do!
>> in .Net 1.1...
>> To solve your issue, you have to intercept and process the reports using
>> your own webpages and not authorize the user to access your report server
>> directly.
>> (the user must go through your own pages, so you control which credential
>> will be used to access reportserver instead of prompting the user)
>>
>> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
>> news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
>> > Hello,
>> >
>> > We are trying to avoid the login pop-up when using the report viewer
>> > control
>> > from an internet facing solution. Sorry it is long, but here is the
>> > scenario.
>> >
>> > ServerA (the webserver, windows 2000 server, v1.1 framework) is serving
>> > a
>> > legacy ASP application that we have added an ASP.NET page that uses the
>> > report viewer control to connect to ServerB.
>> >
>> > ServerB (the report server, windows 2003 server SP1, RS Standard
>> > Edition
>> > SP2) there is a public IP that is Nat's to a local IP of ServerB. This
>> > is
>> > what the report viewer control uses from ServerA. ServerB has a local
>> > user
>> > that has full access to the reports that need to be delivered.
>> >
>> > When you first try to access the report server (ServerB) from the
>> > internet
>> > it prompts for a username and password. Once the local user's
>> > credentials
>> > from ServerB have been entered we are able to view all reports until
>> > the
>> > browser is closed. We have RS 2000 Standard Edition so there is no
>> > option
>> > for
>> > a custom security extension.
>> >
>> > Is there anyway that we can avoid forcing the web users to type in the
>> > username and password that was setup on ServerB? I have tried
>> > everything
>> > I
>> > can think of and have had no success. There are many security issues
>> > with
>> > making that RS login public using URL access and even more security
>> > issues
>> > by
>> > making the report server allow anonymous access. I need a solution!
>> >
>> > Any help would be greatly appreciated.
>> >
>> > Thanks in advance!
>>|||Hello,
Do you have links to any samples using the SOAP API? Do you still have the
option to show the toolbar, hide parameters, etc. like the URL access?
Thanks!
"Jéjé" wrote:
> this control use an IFrame to render the report.
> this IFrame "redirect" the user to RS directly.
> To override this issue you have to open your pages on the ServerA web site
> and disallow the users to access the serverb directly.
> To do this, you have to render the reports by yourself using your own ASPX
> page(s) (you have to call the SOAP API and not use the URL access)
> another way...
> look at this reverse proxy tool:
> http://www.saltypickle.com/Home/16
>
> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
> news:059772D9-D2AF-4725-A036-D8AB78B9CE04@.microsoft.com...
> > Users on serverA are authenticated with a custom SQL login from the ASP
> > pages. The entire site on serverA is classic ASP. We are trying to add
> > the
> > ASPX page with the report viewer control. We are able to determine if the
> > users are authenticated once they hit the ASPX/Report Viewer page.
> >
> > We are using the 1.1 version of the report viewer control that came with
> > SP1
> > or SP2 for RS 2000.
> >
> > Once the web user accesses our ASPX page with the report viewer control
> > how
> > do we set the credentials that access the report server via URL? That is
> > were everything stops working as planned and the standard login pop-up
> > shows.
> > You can type the credentials of the user we want them to access with and
> > everything works fine from that point forward. But we want to set the
> > credentials in the code-behind of the page and not make the credentials
> > publicly available.
> >
> > Any help you could provide to set the credentials that will be used by the
> > report viewer control would be greatly appreciated. I have poured many
> > hours
> > into these reports and the integration with the classic ASP site. The
> > reports use custom assemblies to dynamically build the SQL statements,
> > etc.
> > but now I can't get internet access to them using the report viewer
> > without
> > manually typing in the credentials!
> >
> > Thank you very much.
> >
> >
> > "Jéjé" wrote:
> >
> >> how your users are authenticated on the serverA?
> >> (form authentication or basic authentication?)
> >>
> >> The reportviewer webcontrol is a ASP.Net 2.0 control.
> >> do you use another version?
> >> the .Net 2 version is great, because this version will do what you want
> >> to
> >> do!
> >>
> >> in .Net 1.1...
> >> To solve your issue, you have to intercept and process the reports using
> >> your own webpages and not authorize the user to access your report server
> >> directly.
> >> (the user must go through your own pages, so you control which credential
> >> will be used to access reportserver instead of prompting the user)
> >>
> >>
> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
> >> news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
> >> > Hello,
> >> >
> >> > We are trying to avoid the login pop-up when using the report viewer
> >> > control
> >> > from an internet facing solution. Sorry it is long, but here is the
> >> > scenario.
> >> >
> >> > ServerA (the webserver, windows 2000 server, v1.1 framework) is serving
> >> > a
> >> > legacy ASP application that we have added an ASP.NET page that uses the
> >> > report viewer control to connect to ServerB.
> >> >
> >> > ServerB (the report server, windows 2003 server SP1, RS Standard
> >> > Edition
> >> > SP2) there is a public IP that is Nat's to a local IP of ServerB. This
> >> > is
> >> > what the report viewer control uses from ServerA. ServerB has a local
> >> > user
> >> > that has full access to the reports that need to be delivered.
> >> >
> >> > When you first try to access the report server (ServerB) from the
> >> > internet
> >> > it prompts for a username and password. Once the local user's
> >> > credentials
> >> > from ServerB have been entered we are able to view all reports until
> >> > the
> >> > browser is closed. We have RS 2000 Standard Edition so there is no
> >> > option
> >> > for
> >> > a custom security extension.
> >> >
> >> > Is there anyway that we can avoid forcing the web users to type in the
> >> > username and password that was setup on ServerB? I have tried
> >> > everything
> >> > I
> >> > can think of and have had no success. There are many security issues
> >> > with
> >> > making that RS login public using URL access and even more security
> >> > issues
> >> > by
> >> > making the report server allow anonymous access. I need a solution!
> >> >
> >> > Any help would be greatly appreciated.
> >> >
> >> > Thanks in advance!
> >>
> >>
> >>
>
>|||you have to develop the parameters interface.
there is samples on the web and in RS books
a good sample:
http://www.codeproject.com/aspnet/SQLRSViewer.asp
"Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
news:3687F13F-9CE3-4B3A-9F50-CB942D5CEF2C@.microsoft.com...
> Hello,
> Do you have links to any samples using the SOAP API? Do you still have
> the
> option to show the toolbar, hide parameters, etc. like the URL access?
> Thanks!
> "Jéjé" wrote:
>> this control use an IFrame to render the report.
>> this IFrame "redirect" the user to RS directly.
>> To override this issue you have to open your pages on the ServerA web
>> site
>> and disallow the users to access the serverb directly.
>> To do this, you have to render the reports by yourself using your own
>> ASPX
>> page(s) (you have to call the SOAP API and not use the URL access)
>> another way...
>> look at this reverse proxy tool:
>> http://www.saltypickle.com/Home/16
>>
>> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
>> news:059772D9-D2AF-4725-A036-D8AB78B9CE04@.microsoft.com...
>> > Users on serverA are authenticated with a custom SQL login from the ASP
>> > pages. The entire site on serverA is classic ASP. We are trying to
>> > add
>> > the
>> > ASPX page with the report viewer control. We are able to determine if
>> > the
>> > users are authenticated once they hit the ASPX/Report Viewer page.
>> >
>> > We are using the 1.1 version of the report viewer control that came
>> > with
>> > SP1
>> > or SP2 for RS 2000.
>> >
>> > Once the web user accesses our ASPX page with the report viewer control
>> > how
>> > do we set the credentials that access the report server via URL? That
>> > is
>> > were everything stops working as planned and the standard login pop-up
>> > shows.
>> > You can type the credentials of the user we want them to access with
>> > and
>> > everything works fine from that point forward. But we want to set the
>> > credentials in the code-behind of the page and not make the credentials
>> > publicly available.
>> >
>> > Any help you could provide to set the credentials that will be used by
>> > the
>> > report viewer control would be greatly appreciated. I have poured many
>> > hours
>> > into these reports and the integration with the classic ASP site. The
>> > reports use custom assemblies to dynamically build the SQL statements,
>> > etc.
>> > but now I can't get internet access to them using the report viewer
>> > without
>> > manually typing in the credentials!
>> >
>> > Thank you very much.
>> >
>> >
>> > "Jéjé" wrote:
>> >
>> >> how your users are authenticated on the serverA?
>> >> (form authentication or basic authentication?)
>> >>
>> >> The reportviewer webcontrol is a ASP.Net 2.0 control.
>> >> do you use another version?
>> >> the .Net 2 version is great, because this version will do what you
>> >> want
>> >> to
>> >> do!
>> >>
>> >> in .Net 1.1...
>> >> To solve your issue, you have to intercept and process the reports
>> >> using
>> >> your own webpages and not authorize the user to access your report
>> >> server
>> >> directly.
>> >> (the user must go through your own pages, so you control which
>> >> credential
>> >> will be used to access reportserver instead of prompting the user)
>> >>
>> >>
>> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in
>> >> message
>> >> news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
>> >> > Hello,
>> >> >
>> >> > We are trying to avoid the login pop-up when using the report viewer
>> >> > control
>> >> > from an internet facing solution. Sorry it is long, but here is the
>> >> > scenario.
>> >> >
>> >> > ServerA (the webserver, windows 2000 server, v1.1 framework) is
>> >> > serving
>> >> > a
>> >> > legacy ASP application that we have added an ASP.NET page that uses
>> >> > the
>> >> > report viewer control to connect to ServerB.
>> >> >
>> >> > ServerB (the report server, windows 2003 server SP1, RS Standard
>> >> > Edition
>> >> > SP2) there is a public IP that is Nat's to a local IP of ServerB.
>> >> > This
>> >> > is
>> >> > what the report viewer control uses from ServerA. ServerB has a
>> >> > local
>> >> > user
>> >> > that has full access to the reports that need to be delivered.
>> >> >
>> >> > When you first try to access the report server (ServerB) from the
>> >> > internet
>> >> > it prompts for a username and password. Once the local user's
>> >> > credentials
>> >> > from ServerB have been entered we are able to view all reports until
>> >> > the
>> >> > browser is closed. We have RS 2000 Standard Edition so there is no
>> >> > option
>> >> > for
>> >> > a custom security extension.
>> >> >
>> >> > Is there anyway that we can avoid forcing the web users to type in
>> >> > the
>> >> > username and password that was setup on ServerB? I have tried
>> >> > everything
>> >> > I
>> >> > can think of and have had no success. There are many security
>> >> > issues
>> >> > with
>> >> > making that RS login public using URL access and even more security
>> >> > issues
>> >> > by
>> >> > making the report server allow anonymous access. I need a solution!
>> >> >
>> >> > Any help would be greatly appreciated.
>> >> >
>> >> > Thanks in advance!
>> >>
>> >>
>> >>
>>|||Hello,
I just wanted to confirm that there will be no limitations using the SOAP
API with the Standard version of reporting services. The reason I ask is
that in many of the different solutions I have tried the "this is not
supported in this version" has come up. I tried the logonuser method
connecting to the web service and received a similar error. I was trying to
connect and logon prior to connecting with the report viewer control hoping
that would save the authentication like manually typing in the credentials
does. You only have to manually type them in once, but that is too many!
The sad thing about it is that with all the hours wasted trying to get the
Standard Edition to work we probably could have simply purchased the
Enterprise Edition, used forms authentication and deployed the solution
months ago!
Thanks for all your assistance!
"Jéjé" wrote:
> you have to develop the parameters interface.
> there is samples on the web and in RS books
> a good sample:
> http://www.codeproject.com/aspnet/SQLRSViewer.asp
>
> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
> news:3687F13F-9CE3-4B3A-9F50-CB942D5CEF2C@.microsoft.com...
> > Hello,
> >
> > Do you have links to any samples using the SOAP API? Do you still have
> > the
> > option to show the toolbar, hide parameters, etc. like the URL access?
> >
> > Thanks!
> >
> > "Jéjé" wrote:
> >
> >> this control use an IFrame to render the report.
> >> this IFrame "redirect" the user to RS directly.
> >>
> >> To override this issue you have to open your pages on the ServerA web
> >> site
> >> and disallow the users to access the serverb directly.
> >> To do this, you have to render the reports by yourself using your own
> >> ASPX
> >> page(s) (you have to call the SOAP API and not use the URL access)
> >>
> >> another way...
> >> look at this reverse proxy tool:
> >> http://www.saltypickle.com/Home/16
> >>
> >>
> >>
> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
> >> news:059772D9-D2AF-4725-A036-D8AB78B9CE04@.microsoft.com...
> >> > Users on serverA are authenticated with a custom SQL login from the ASP
> >> > pages. The entire site on serverA is classic ASP. We are trying to
> >> > add
> >> > the
> >> > ASPX page with the report viewer control. We are able to determine if
> >> > the
> >> > users are authenticated once they hit the ASPX/Report Viewer page.
> >> >
> >> > We are using the 1.1 version of the report viewer control that came
> >> > with
> >> > SP1
> >> > or SP2 for RS 2000.
> >> >
> >> > Once the web user accesses our ASPX page with the report viewer control
> >> > how
> >> > do we set the credentials that access the report server via URL? That
> >> > is
> >> > were everything stops working as planned and the standard login pop-up
> >> > shows.
> >> > You can type the credentials of the user we want them to access with
> >> > and
> >> > everything works fine from that point forward. But we want to set the
> >> > credentials in the code-behind of the page and not make the credentials
> >> > publicly available.
> >> >
> >> > Any help you could provide to set the credentials that will be used by
> >> > the
> >> > report viewer control would be greatly appreciated. I have poured many
> >> > hours
> >> > into these reports and the integration with the classic ASP site. The
> >> > reports use custom assemblies to dynamically build the SQL statements,
> >> > etc.
> >> > but now I can't get internet access to them using the report viewer
> >> > without
> >> > manually typing in the credentials!
> >> >
> >> > Thank you very much.
> >> >
> >> >
> >> > "Jéjé" wrote:
> >> >
> >> >> how your users are authenticated on the serverA?
> >> >> (form authentication or basic authentication?)
> >> >>
> >> >> The reportviewer webcontrol is a ASP.Net 2.0 control.
> >> >> do you use another version?
> >> >> the .Net 2 version is great, because this version will do what you
> >> >> want
> >> >> to
> >> >> do!
> >> >>
> >> >> in .Net 1.1...
> >> >> To solve your issue, you have to intercept and process the reports
> >> >> using
> >> >> your own webpages and not authorize the user to access your report
> >> >> server
> >> >> directly.
> >> >> (the user must go through your own pages, so you control which
> >> >> credential
> >> >> will be used to access reportserver instead of prompting the user)
> >> >>
> >> >>
> >> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
> >> >> > Hello,
> >> >> >
> >> >> > We are trying to avoid the login pop-up when using the report viewer
> >> >> > control
> >> >> > from an internet facing solution. Sorry it is long, but here is the
> >> >> > scenario.
> >> >> >
> >> >> > ServerA (the webserver, windows 2000 server, v1.1 framework) is
> >> >> > serving
> >> >> > a
> >> >> > legacy ASP application that we have added an ASP.NET page that uses
> >> >> > the
> >> >> > report viewer control to connect to ServerB.
> >> >> >
> >> >> > ServerB (the report server, windows 2003 server SP1, RS Standard
> >> >> > Edition
> >> >> > SP2) there is a public IP that is Nat's to a local IP of ServerB.
> >> >> > This
> >> >> > is
> >> >> > what the report viewer control uses from ServerA. ServerB has a
> >> >> > local
> >> >> > user
> >> >> > that has full access to the reports that need to be delivered.
> >> >> >
> >> >> > When you first try to access the report server (ServerB) from the
> >> >> > internet
> >> >> > it prompts for a username and password. Once the local user's
> >> >> > credentials
> >> >> > from ServerB have been entered we are able to view all reports until
> >> >> > the
> >> >> > browser is closed. We have RS 2000 Standard Edition so there is no
> >> >> > option
> >> >> > for
> >> >> > a custom security extension.
> >> >> >
> >> >> > Is there anyway that we can avoid forcing the web users to type in
> >> >> > the
> >> >> > username and password that was setup on ServerB? I have tried
> >> >> > everything
> >> >> > I
> >> >> > can think of and have had no success. There are many security
> >> >> > issues
> >> >> > with
> >> >> > making that RS login public using URL access and even more security
> >> >> > issues
> >> >> > by
> >> >> > making the report server allow anonymous access. I need a solution!
> >> >> >
> >> >> > Any help would be greatly appreciated.
> >> >> >
> >> >> > Thanks in advance!
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||the SOAP API is available in any edition.
the link sent to you can be used with any version of RS
when you call the RS webservice, create a specific credential or use the
impersonate account setup in the web.config file
read this:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetch10.asp
(the section called "Using specific credentials")
so your application continue to use your own authentication system and
you'll control all the access to RS through your application.
The only limitation:
you can't use the User!UserID in your reports, you have to change this by a
a standard report parameter and fill this parameter in your web application
without displaying this parameter to the end user.
"Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
news:C3FA0554-12EA-4AC3-893C-4DD5AD99A517@.microsoft.com...
> Hello,
> I just wanted to confirm that there will be no limitations using the SOAP
> API with the Standard version of reporting services. The reason I ask is
> that in many of the different solutions I have tried the "this is not
> supported in this version" has come up. I tried the logonuser method
> connecting to the web service and received a similar error. I was trying
> to
> connect and logon prior to connecting with the report viewer control
> hoping
> that would save the authentication like manually typing in the credentials
> does. You only have to manually type them in once, but that is too many!
> The sad thing about it is that with all the hours wasted trying to get the
> Standard Edition to work we probably could have simply purchased the
> Enterprise Edition, used forms authentication and deployed the solution
> months ago!
> Thanks for all your assistance!
>
> "Jéjé" wrote:
>> you have to develop the parameters interface.
>> there is samples on the web and in RS books
>> a good sample:
>> http://www.codeproject.com/aspnet/SQLRSViewer.asp
>>
>> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
>> news:3687F13F-9CE3-4B3A-9F50-CB942D5CEF2C@.microsoft.com...
>> > Hello,
>> >
>> > Do you have links to any samples using the SOAP API? Do you still have
>> > the
>> > option to show the toolbar, hide parameters, etc. like the URL access?
>> >
>> > Thanks!
>> >
>> > "Jéjé" wrote:
>> >
>> >> this control use an IFrame to render the report.
>> >> this IFrame "redirect" the user to RS directly.
>> >>
>> >> To override this issue you have to open your pages on the ServerA web
>> >> site
>> >> and disallow the users to access the serverb directly.
>> >> To do this, you have to render the reports by yourself using your own
>> >> ASPX
>> >> page(s) (you have to call the SOAP API and not use the URL access)
>> >>
>> >> another way...
>> >> look at this reverse proxy tool:
>> >> http://www.saltypickle.com/Home/16
>> >>
>> >>
>> >>
>> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in
>> >> message
>> >> news:059772D9-D2AF-4725-A036-D8AB78B9CE04@.microsoft.com...
>> >> > Users on serverA are authenticated with a custom SQL login from the
>> >> > ASP
>> >> > pages. The entire site on serverA is classic ASP. We are trying to
>> >> > add
>> >> > the
>> >> > ASPX page with the report viewer control. We are able to determine
>> >> > if
>> >> > the
>> >> > users are authenticated once they hit the ASPX/Report Viewer page.
>> >> >
>> >> > We are using the 1.1 version of the report viewer control that came
>> >> > with
>> >> > SP1
>> >> > or SP2 for RS 2000.
>> >> >
>> >> > Once the web user accesses our ASPX page with the report viewer
>> >> > control
>> >> > how
>> >> > do we set the credentials that access the report server via URL?
>> >> > That
>> >> > is
>> >> > were everything stops working as planned and the standard login
>> >> > pop-up
>> >> > shows.
>> >> > You can type the credentials of the user we want them to access with
>> >> > and
>> >> > everything works fine from that point forward. But we want to set
>> >> > the
>> >> > credentials in the code-behind of the page and not make the
>> >> > credentials
>> >> > publicly available.
>> >> >
>> >> > Any help you could provide to set the credentials that will be used
>> >> > by
>> >> > the
>> >> > report viewer control would be greatly appreciated. I have poured
>> >> > many
>> >> > hours
>> >> > into these reports and the integration with the classic ASP site.
>> >> > The
>> >> > reports use custom assemblies to dynamically build the SQL
>> >> > statements,
>> >> > etc.
>> >> > but now I can't get internet access to them using the report viewer
>> >> > without
>> >> > manually typing in the credentials!
>> >> >
>> >> > Thank you very much.
>> >> >
>> >> >
>> >> > "Jéjé" wrote:
>> >> >
>> >> >> how your users are authenticated on the serverA?
>> >> >> (form authentication or basic authentication?)
>> >> >>
>> >> >> The reportviewer webcontrol is a ASP.Net 2.0 control.
>> >> >> do you use another version?
>> >> >> the .Net 2 version is great, because this version will do what you
>> >> >> want
>> >> >> to
>> >> >> do!
>> >> >>
>> >> >> in .Net 1.1...
>> >> >> To solve your issue, you have to intercept and process the reports
>> >> >> using
>> >> >> your own webpages and not authorize the user to access your report
>> >> >> server
>> >> >> directly.
>> >> >> (the user must go through your own pages, so you control which
>> >> >> credential
>> >> >> will be used to access reportserver instead of prompting the user)
>> >> >>
>> >> >>
>> >> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
>> >> >> > Hello,
>> >> >> >
>> >> >> > We are trying to avoid the login pop-up when using the report
>> >> >> > viewer
>> >> >> > control
>> >> >> > from an internet facing solution. Sorry it is long, but here is
>> >> >> > the
>> >> >> > scenario.
>> >> >> >
>> >> >> > ServerA (the webserver, windows 2000 server, v1.1 framework) is
>> >> >> > serving
>> >> >> > a
>> >> >> > legacy ASP application that we have added an ASP.NET page that
>> >> >> > uses
>> >> >> > the
>> >> >> > report viewer control to connect to ServerB.
>> >> >> >
>> >> >> > ServerB (the report server, windows 2003 server SP1, RS Standard
>> >> >> > Edition
>> >> >> > SP2) there is a public IP that is Nat's to a local IP of ServerB.
>> >> >> > This
>> >> >> > is
>> >> >> > what the report viewer control uses from ServerA. ServerB has a
>> >> >> > local
>> >> >> > user
>> >> >> > that has full access to the reports that need to be delivered.
>> >> >> >
>> >> >> > When you first try to access the report server (ServerB) from the
>> >> >> > internet
>> >> >> > it prompts for a username and password. Once the local user's
>> >> >> > credentials
>> >> >> > from ServerB have been entered we are able to view all reports
>> >> >> > until
>> >> >> > the
>> >> >> > browser is closed. We have RS 2000 Standard Edition so there is
>> >> >> > no
>> >> >> > option
>> >> >> > for
>> >> >> > a custom security extension.
>> >> >> >
>> >> >> > Is there anyway that we can avoid forcing the web users to type
>> >> >> > in
>> >> >> > the
>> >> >> > username and password that was setup on ServerB? I have tried
>> >> >> > everything
>> >> >> > I
>> >> >> > can think of and have had no success. There are many security
>> >> >> > issues
>> >> >> > with
>> >> >> > making that RS login public using URL access and even more
>> >> >> > security
>> >> >> > issues
>> >> >> > by
>> >> >> > making the report server allow anonymous access. I need a
>> >> >> > solution!
>> >> >> >
>> >> >> > Any help would be greatly appreciated.
>> >> >> >
>> >> >> > Thanks in advance!
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Thanks again for all your help!
"Jéjé" wrote:
> the SOAP API is available in any edition.
> the link sent to you can be used with any version of RS
> when you call the RS webservice, create a specific credential or use the
> impersonate account setup in the web.config file
> read this:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetch10.asp
> (the section called "Using specific credentials")
> so your application continue to use your own authentication system and
> you'll control all the access to RS through your application.
> The only limitation:
> you can't use the User!UserID in your reports, you have to change this by a
> a standard report parameter and fill this parameter in your web application
> without displaying this parameter to the end user.
>
> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
> news:C3FA0554-12EA-4AC3-893C-4DD5AD99A517@.microsoft.com...
> > Hello,
> >
> > I just wanted to confirm that there will be no limitations using the SOAP
> > API with the Standard version of reporting services. The reason I ask is
> > that in many of the different solutions I have tried the "this is not
> > supported in this version" has come up. I tried the logonuser method
> > connecting to the web service and received a similar error. I was trying
> > to
> > connect and logon prior to connecting with the report viewer control
> > hoping
> > that would save the authentication like manually typing in the credentials
> > does. You only have to manually type them in once, but that is too many!
> >
> > The sad thing about it is that with all the hours wasted trying to get the
> > Standard Edition to work we probably could have simply purchased the
> > Enterprise Edition, used forms authentication and deployed the solution
> > months ago!
> >
> > Thanks for all your assistance!
> >
> >
> > "Jéjé" wrote:
> >
> >> you have to develop the parameters interface.
> >>
> >> there is samples on the web and in RS books
> >>
> >> a good sample:
> >> http://www.codeproject.com/aspnet/SQLRSViewer.asp
> >>
> >>
> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
> >> news:3687F13F-9CE3-4B3A-9F50-CB942D5CEF2C@.microsoft.com...
> >> > Hello,
> >> >
> >> > Do you have links to any samples using the SOAP API? Do you still have
> >> > the
> >> > option to show the toolbar, hide parameters, etc. like the URL access?
> >> >
> >> > Thanks!
> >> >
> >> > "Jéjé" wrote:
> >> >
> >> >> this control use an IFrame to render the report.
> >> >> this IFrame "redirect" the user to RS directly.
> >> >>
> >> >> To override this issue you have to open your pages on the ServerA web
> >> >> site
> >> >> and disallow the users to access the serverb directly.
> >> >> To do this, you have to render the reports by yourself using your own
> >> >> ASPX
> >> >> page(s) (you have to call the SOAP API and not use the URL access)
> >> >>
> >> >> another way...
> >> >> look at this reverse proxy tool:
> >> >> http://www.saltypickle.com/Home/16
> >> >>
> >> >>
> >> >>
> >> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:059772D9-D2AF-4725-A036-D8AB78B9CE04@.microsoft.com...
> >> >> > Users on serverA are authenticated with a custom SQL login from the
> >> >> > ASP
> >> >> > pages. The entire site on serverA is classic ASP. We are trying to
> >> >> > add
> >> >> > the
> >> >> > ASPX page with the report viewer control. We are able to determine
> >> >> > if
> >> >> > the
> >> >> > users are authenticated once they hit the ASPX/Report Viewer page.
> >> >> >
> >> >> > We are using the 1.1 version of the report viewer control that came
> >> >> > with
> >> >> > SP1
> >> >> > or SP2 for RS 2000.
> >> >> >
> >> >> > Once the web user accesses our ASPX page with the report viewer
> >> >> > control
> >> >> > how
> >> >> > do we set the credentials that access the report server via URL?
> >> >> > That
> >> >> > is
> >> >> > were everything stops working as planned and the standard login
> >> >> > pop-up
> >> >> > shows.
> >> >> > You can type the credentials of the user we want them to access with
> >> >> > and
> >> >> > everything works fine from that point forward. But we want to set
> >> >> > the
> >> >> > credentials in the code-behind of the page and not make the
> >> >> > credentials
> >> >> > publicly available.
> >> >> >
> >> >> > Any help you could provide to set the credentials that will be used
> >> >> > by
> >> >> > the
> >> >> > report viewer control would be greatly appreciated. I have poured
> >> >> > many
> >> >> > hours
> >> >> > into these reports and the integration with the classic ASP site.
> >> >> > The
> >> >> > reports use custom assemblies to dynamically build the SQL
> >> >> > statements,
> >> >> > etc.
> >> >> > but now I can't get internet access to them using the report viewer
> >> >> > without
> >> >> > manually typing in the credentials!
> >> >> >
> >> >> > Thank you very much.
> >> >> >
> >> >> >
> >> >> > "Jéjé" wrote:
> >> >> >
> >> >> >> how your users are authenticated on the serverA?
> >> >> >> (form authentication or basic authentication?)
> >> >> >>
> >> >> >> The reportviewer webcontrol is a ASP.Net 2.0 control.
> >> >> >> do you use another version?
> >> >> >> the .Net 2 version is great, because this version will do what you
> >> >> >> want
> >> >> >> to
> >> >> >> do!
> >> >> >>
> >> >> >> in .Net 1.1...
> >> >> >> To solve your issue, you have to intercept and process the reports
> >> >> >> using
> >> >> >> your own webpages and not authorize the user to access your report
> >> >> >> server
> >> >> >> directly.
> >> >> >> (the user must go through your own pages, so you control which
> >> >> >> credential
> >> >> >> will be used to access reportserver instead of prompting the user)
> >> >> >>
> >> >> >>
> >> >> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
> >> >> >> > Hello,
> >> >> >> >
> >> >> >> > We are trying to avoid the login pop-up when using the report
> >> >> >> > viewer
> >> >> >> > control
> >> >> >> > from an internet facing solution. Sorry it is long, but here is
> >> >> >> > the
> >> >> >> > scenario.
> >> >> >> >
> >> >> >> > ServerA (the webserver, windows 2000 server, v1.1 framework) is
> >> >> >> > serving
> >> >> >> > a
> >> >> >> > legacy ASP application that we have added an ASP.NET page that
> >> >> >> > uses
> >> >> >> > the
> >> >> >> > report viewer control to connect to ServerB.
> >> >> >> >
> >> >> >> > ServerB (the report server, windows 2003 server SP1, RS Standard
> >> >> >> > Edition
> >> >> >> > SP2) there is a public IP that is Nat's to a local IP of ServerB.
> >> >> >> > This
> >> >> >> > is
> >> >> >> > what the report viewer control uses from ServerA. ServerB has a
> >> >> >> > local
> >> >> >> > user
> >> >> >> > that has full access to the reports that need to be delivered.
> >> >> >> >
> >> >> >> > When you first try to access the report server (ServerB) from the
> >> >> >> > internet
> >> >> >> > it prompts for a username and password. Once the local user's
> >> >> >> > credentials
> >> >> >> > from ServerB have been entered we are able to view all reports
> >> >> >> > until
> >> >> >> > the
> >> >> >> > browser is closed. We have RS 2000 Standard Edition so there is
> >> >> >> > no
> >> >> >> > option
> >> >> >> > for
> >> >> >> > a custom security extension.
> >> >> >> >
> >> >> >> > Is there anyway that we can avoid forcing the web users to type
> >> >> >> > in
> >> >> >> > the
> >> >> >> > username and password that was setup on ServerB? I have tried
> >> >> >> > everything
> >> >> >> > I
> >> >> >> > can think of and have had no success. There are many security
> >> >> >> > issues
> >> >> >> > with
> >> >> >> > making that RS login public using URL access and even more
> >> >> >> > security
> >> >> >> > issues
> >> >> >> > by
> >> >> >> > making the report server allow anonymous access. I need a
> >> >> >> > solution!
> >> >> >> >
> >> >> >> > Any help would be greatly appreciated.
> >> >> >> >
> >> >> >> > Thanks in advance!
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||A big setback with using SOAP API is that you lose the report toolbar.
"Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
news:68B042E6-912D-4F08-8C81-C77F2F9BDD82@.microsoft.com...
> Thanks again for all your help!
> "Jéjé" wrote:
>> the SOAP API is available in any edition.
>> the link sent to you can be used with any version of RS
>> when you call the RS webservice, create a specific credential or use the
>> impersonate account setup in the web.config file
>> read this:
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetch10.asp
>> (the section called "Using specific credentials")
>> so your application continue to use your own authentication system and
>> you'll control all the access to RS through your application.
>> The only limitation:
>> you can't use the User!UserID in your reports, you have to change this by
>> a
>> a standard report parameter and fill this parameter in your web
>> application
>> without displaying this parameter to the end user.
>>
>> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in message
>> news:C3FA0554-12EA-4AC3-893C-4DD5AD99A517@.microsoft.com...
>> > Hello,
>> >
>> > I just wanted to confirm that there will be no limitations using the
>> > SOAP
>> > API with the Standard version of reporting services. The reason I ask
>> > is
>> > that in many of the different solutions I have tried the "this is not
>> > supported in this version" has come up. I tried the logonuser method
>> > connecting to the web service and received a similar error. I was
>> > trying
>> > to
>> > connect and logon prior to connecting with the report viewer control
>> > hoping
>> > that would save the authentication like manually typing in the
>> > credentials
>> > does. You only have to manually type them in once, but that is too
>> > many!
>> >
>> > The sad thing about it is that with all the hours wasted trying to get
>> > the
>> > Standard Edition to work we probably could have simply purchased the
>> > Enterprise Edition, used forms authentication and deployed the solution
>> > months ago!
>> >
>> > Thanks for all your assistance!
>> >
>> >
>> > "Jéjé" wrote:
>> >
>> >> you have to develop the parameters interface.
>> >>
>> >> there is samples on the web and in RS books
>> >>
>> >> a good sample:
>> >> http://www.codeproject.com/aspnet/SQLRSViewer.asp
>> >>
>> >>
>> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in
>> >> message
>> >> news:3687F13F-9CE3-4B3A-9F50-CB942D5CEF2C@.microsoft.com...
>> >> > Hello,
>> >> >
>> >> > Do you have links to any samples using the SOAP API? Do you still
>> >> > have
>> >> > the
>> >> > option to show the toolbar, hide parameters, etc. like the URL
>> >> > access?
>> >> >
>> >> > Thanks!
>> >> >
>> >> > "Jéjé" wrote:
>> >> >
>> >> >> this control use an IFrame to render the report.
>> >> >> this IFrame "redirect" the user to RS directly.
>> >> >>
>> >> >> To override this issue you have to open your pages on the ServerA
>> >> >> web
>> >> >> site
>> >> >> and disallow the users to access the serverb directly.
>> >> >> To do this, you have to render the reports by yourself using your
>> >> >> own
>> >> >> ASPX
>> >> >> page(s) (you have to call the SOAP API and not use the URL access)
>> >> >>
>> >> >> another way...
>> >> >> look at this reverse proxy tool:
>> >> >> http://www.saltypickle.com/Home/16
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:059772D9-D2AF-4725-A036-D8AB78B9CE04@.microsoft.com...
>> >> >> > Users on serverA are authenticated with a custom SQL login from
>> >> >> > the
>> >> >> > ASP
>> >> >> > pages. The entire site on serverA is classic ASP. We are trying
>> >> >> > to
>> >> >> > add
>> >> >> > the
>> >> >> > ASPX page with the report viewer control. We are able to
>> >> >> > determine
>> >> >> > if
>> >> >> > the
>> >> >> > users are authenticated once they hit the ASPX/Report Viewer
>> >> >> > page.
>> >> >> >
>> >> >> > We are using the 1.1 version of the report viewer control that
>> >> >> > came
>> >> >> > with
>> >> >> > SP1
>> >> >> > or SP2 for RS 2000.
>> >> >> >
>> >> >> > Once the web user accesses our ASPX page with the report viewer
>> >> >> > control
>> >> >> > how
>> >> >> > do we set the credentials that access the report server via URL?
>> >> >> > That
>> >> >> > is
>> >> >> > were everything stops working as planned and the standard login
>> >> >> > pop-up
>> >> >> > shows.
>> >> >> > You can type the credentials of the user we want them to access
>> >> >> > with
>> >> >> > and
>> >> >> > everything works fine from that point forward. But we want to
>> >> >> > set
>> >> >> > the
>> >> >> > credentials in the code-behind of the page and not make the
>> >> >> > credentials
>> >> >> > publicly available.
>> >> >> >
>> >> >> > Any help you could provide to set the credentials that will be
>> >> >> > used
>> >> >> > by
>> >> >> > the
>> >> >> > report viewer control would be greatly appreciated. I have
>> >> >> > poured
>> >> >> > many
>> >> >> > hours
>> >> >> > into these reports and the integration with the classic ASP site.
>> >> >> > The
>> >> >> > reports use custom assemblies to dynamically build the SQL
>> >> >> > statements,
>> >> >> > etc.
>> >> >> > but now I can't get internet access to them using the report
>> >> >> > viewer
>> >> >> > without
>> >> >> > manually typing in the credentials!
>> >> >> >
>> >> >> > Thank you very much.
>> >> >> >
>> >> >> >
>> >> >> > "Jéjé" wrote:
>> >> >> >
>> >> >> >> how your users are authenticated on the serverA?
>> >> >> >> (form authentication or basic authentication?)
>> >> >> >>
>> >> >> >> The reportviewer webcontrol is a ASP.Net 2.0 control.
>> >> >> >> do you use another version?
>> >> >> >> the .Net 2 version is great, because this version will do what
>> >> >> >> you
>> >> >> >> want
>> >> >> >> to
>> >> >> >> do!
>> >> >> >>
>> >> >> >> in .Net 1.1...
>> >> >> >> To solve your issue, you have to intercept and process the
>> >> >> >> reports
>> >> >> >> using
>> >> >> >> your own webpages and not authorize the user to access your
>> >> >> >> report
>> >> >> >> server
>> >> >> >> directly.
>> >> >> >> (the user must go through your own pages, so you control which
>> >> >> >> credential
>> >> >> >> will be used to access reportserver instead of prompting the
>> >> >> >> user)
>> >> >> >>
>> >> >> >>
>> >> >> >> "Chris_CamSoft" <ChrisCamSoft@.discussions.microsoft.com> wrote
>> >> >> >> in
>> >> >> >> message
>> >> >> >> news:96843F84-0BB8-46B4-8BF8-A9488F25A122@.microsoft.com...
>> >> >> >> > Hello,
>> >> >> >> >
>> >> >> >> > We are trying to avoid the login pop-up when using the report
>> >> >> >> > viewer
>> >> >> >> > control
>> >> >> >> > from an internet facing solution. Sorry it is long, but here
>> >> >> >> > is
>> >> >> >> > the
>> >> >> >> > scenario.
>> >> >> >> >
>> >> >> >> > ServerA (the webserver, windows 2000 server, v1.1 framework)
>> >> >> >> > is
>> >> >> >> > serving
>> >> >> >> > a
>> >> >> >> > legacy ASP application that we have added an ASP.NET page that
>> >> >> >> > uses
>> >> >> >> > the
>> >> >> >> > report viewer control to connect to ServerB.
>> >> >> >> >
>> >> >> >> > ServerB (the report server, windows 2003 server SP1, RS
>> >> >> >> > Standard
>> >> >> >> > Edition
>> >> >> >> > SP2) there is a public IP that is Nat's to a local IP of
>> >> >> >> > ServerB.
>> >> >> >> > This
>> >> >> >> > is
>> >> >> >> > what the report viewer control uses from ServerA. ServerB has
>> >> >> >> > a
>> >> >> >> > local
>> >> >> >> > user
>> >> >> >> > that has full access to the reports that need to be delivered.
>> >> >> >> >
>> >> >> >> > When you first try to access the report server (ServerB) from
>> >> >> >> > the
>> >> >> >> > internet
>> >> >> >> > it prompts for a username and password. Once the local user's
>> >> >> >> > credentials
>> >> >> >> > from ServerB have been entered we are able to view all reports
>> >> >> >> > until
>> >> >> >> > the
>> >> >> >> > browser is closed. We have RS 2000 Standard Edition so there
>> >> >> >> > is
>> >> >> >> > no
>> >> >> >> > option
>> >> >> >> > for
>> >> >> >> > a custom security extension.
>> >> >> >> >
>> >> >> >> > Is there anyway that we can avoid forcing the web users to
>> >> >> >> > type
>> >> >> >> > in
>> >> >> >> > the
>> >> >> >> > username and password that was setup on ServerB? I have tried
>> >> >> >> > everything
>> >> >> >> > I
>> >> >> >> > can think of and have had no success. There are many security
>> >> >> >> > issues
>> >> >> >> > with
>> >> >> >> > making that RS login public using URL access and even more
>> >> >> >> > security
>> >> >> >> > issues
>> >> >> >> > by
>> >> >> >> > making the report server allow anonymous access. I need a
>> >> >> >> > solution!
>> >> >> >> >
>> >> >> >> > Any help would be greatly appreciated.
>> >> >> >> >
>> >> >> >> > Thanks in advance!
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>

Report Viewer on Internet Site

Hi, I am developing a website that will use the VS Report Viewer control to display some business reports.....The website will be on the internet, but the report viewer will need to access an internal report server that the internet users don't have access to? Is this possible, or the correct way to do this? Any ideas / suggestions would be appreciated!

Cheers
Chris

If you use anonymous access then the user who is accessing the report from the internet does not have to authenticate any type of username to the server.

However, you probably don't want just ANYONE to see your reports, so you may want to develop a secure front-end with Visual Studio to authenticate the user in that fashion. Sort of like a portal on a website. If you go this route, be sure to use a stored procedure and possibly encryption for your password I/O.

Report Viewer access permissions problem

Hi,
I have a Report Viewer intergrated in my application and deployed on server. When I try to access that from internet it says Network/Service account has not enough permission to run that task. Any idea how to give rights to SQL Server 2005 Service account to run reports from internet.

Thanks

add the NT AUTHORITY\NETWORK SERVICE as USER to your db|||

Hi,

Thanks for the reply

I already added NT AUTHORITY\NETWORK SERVICE as user for DB but when loading report from web page that its says that NT AUTHORITY\NETWORK SERVICE dont have enough permission to run that task for report viewer. Please any idea

Thanks

sql

Report Title in Internet Explorer Tab

Is there a way to show the report title in an Internet Explorer tab instead
of having it render "Report Viewer"? Seems that users are opening many
reports and it is hard to find the one you want with many windows open. Any
Thoughts?
Thanks
RickOn Nov 2, 1:41 pm, Rick Spicknall
<RickSpickn...@.discussions.microsoft.com> wrote:
> Is there a way to show the report title in an Internet Explorer tab instead
> of having it render "Report Viewer"? Seems that users are opening many
> reports and it is hard to find the one you want with many windows open. Any
> Thoughts?
> Thanks
> Rick
As far as I know, there is not. The closest thing you will be able to
do is export the report(s) to Web Archive (MHTML) and the report name
itself will appear in the IE tab. Of course, if you are willing to
render the reports to web archive programmatically, you can build an
ASP.NET application that allows you to append HTML to the web archive
output (via possibly: Streamreader, Stringbuilder.Append and
Streamwriter) and try to create the IE tabs from the Report Title
information. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Report Server Authentication through Internet

We're trying to determine the best way to implement an authentication mechanism for our reporting services solution. Basically, we are exposing a web application to the internet, and allowing a forms authenticated user to access our report server somewhere within our intranet to view reports. I've browsed msdn and found that there are two approaches:

1. create a custom authentication extension for reporting services
2. create a restricted domain user that is allowed to access the report server

Going with approach 2 and assuming I'm using a ReportViewer control, in order to authenticate with the report server (using the one domain user created specifically for report server access), are we supposed to just provide an instance of an object implementing IReportServerCredential containing the domain user information to the Credentials property of the ReportViewer.ServerReport before accessing the report? Is this the correct way to implement approach 2? Also, if implementing approach 2 is so simple compared to approach 1, why would anyone choose to implement custom authentication extension if they don't need fine-grain access control on the report server level?

Thanks for any help and suggestions!If you use IReportServerCredential you essentially implement basic security since you need the user id and password. Instead, I'd recommend you use the identity of the asp.net process (application domain in IIS 6.0). You will need custom security if you need to propagate the user identity to the Report Server so RS can tell the users appart. If you don't need this then trusted account will be the recommended approach. You may find the following article useful.|||Thanks for the reply, Teo.

I read the article. So are you recommending that we run the ASP.Net process, hosting our custom application, under some domain account to grant it access to RS? Are there any security risks using this approach where we are granting the process (and all applications running under it in IIS 5.0, and at least the entire application pool itself in IIS 6.0) domain access? Or am I just misunderstanding this approach entirely? Thanks again for the help!|||Just to note that it doesn't have to be a domain account if the app and RS are on the same machine. Inherently, this approach is more secure because you don't need to deal with passwords.|||Hi Teo, thanks again for the reply.

The App and RS will be on separate machines. The App will be on a internet-facing webserver, whereas RS will be somewhere in an domain-access only machine. So I'm guessing I must run the App under a domain account.

How safe it is to have the domain account's user/pass stored in an encrypted .config file on the webserver machine, which would be read and passed (ie. basic) to RS for authentication on an domain-access only machine? And since I'm only passing these credentials between machines within my domain, isn't the passing of the credentials quite safe? And also this way, isn't it safer that the process running the application does not have more rights than it should at any time, while access to domain/RS is granted to the user only on a on-demand basis?

Sorry for asking so many questions.. I just want to understand all the pros and cons of each approach. Thanks a lot for the patience!|||

So I'm guessing I must run the App under a domain account.

Yes, you are right.

How safe it is to have the domain account's user/pass stored in an encrypted .config file on the webserver machine, which would be read and passed (ie. basic) to RS for authentication on an domain-access only machine?

As I mentioned, if you use IReportCredentials in ReportViewer you are essentially using Windows Basic security. The credentials will be passed base64-encoded between the app server and RS. But since this is on your internal LAN, it may not be a huge security risk for you. We followed this pattern with our applicaton for clients who don't have AD. The ReportViewer would read the credentials from a security service (stored in encrypted format), decrypt them and set them on the call.

|||Hi Teo,

Thanks a lot again for the reply.

As

I mentioned, if you use IReportCredentials in ReportViewer you are

essentially using Windows Basic security. The credentials will be

passed base64-encoded between the app server and RS.

Can I setup ReportServer to use SSL to even further secure this portion of the basic authentication within the LAN?
|||Sure, you can.|||Thanks, Teo.

Final question, can you tell me any security risks of running the asp.net under a domain account? Is there any possibility that that identity could be hijacked and maliciously used?|||None that I know of. With IIS 6.0 I recommend you set up a separate application pool. That way the domain identity will be scoped for the application only.|||Hi Teo,
You have answered all my questions. Thanks for all the replies you've given me on this thread. All your suggestions and pointers have been a great help. Thanks!!