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!
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>