Authentication IIS and SSRS

I have two servers IIS Server and SQL2005.
I have web app using ReportViewer on IIS Server to view reports on SQL
Server SSRS.
Both servers are on domain1.
Authentication was not working so on IIS web app in web.config in system.web
I say identity impersonate="true" userName="domain1\username"
password="password" then it works fine -- but is this correct way to do? I
don't like to have to have an account in there that has admin privs -- I
thought it should be just impersonate="true" and not have to send a domain
username/password?
I read many things on nntp about this topic but was unable to finad anything
to work except for the way I have it above.
Thank you!Why dont you enable anonymouse access and give everyone access in the
report server.
dev648237923 wrote:
> I have two servers IIS Server and SQL2005.
> I have web app using ReportViewer on IIS Server to view reports on SQL
> Server SSRS.
> Both servers are on domain1.
> Authentication was not working so on IIS web app in web.config in system.web
> I say identity impersonate="true" userName="domain1\username"
> password="password" then it works fine -- but is this correct way to do? I
> don't like to have to have an account in there that has admin privs -- I
> thought it should be just impersonate="true" and not have to send a domain
> username/password?
> I read many things on nntp about this topic but was unable to finad anything
> to work except for the way I have it above.
> Thank you!|||The Report Server is not exposed to the Internet -- only my web application
can get at it -- more secure that way (so my IIS server is public but the
SQL is not). I followed what Steve said and it worked great!
Thanks.
"sunil.jaikumar" <sunil.jaikumar@.gmail.com> wrote in message
news:1152863352.300856.43580@.m73g2000cwd.googlegroups.com...
> Why dont you enable anonymouse access and give everyone access in the
> report server.
> dev648237923 wrote:
>> I have two servers IIS Server and SQL2005.
>> I have web app using ReportViewer on IIS Server to view reports on SQL
>> Server SSRS.
>> Both servers are on domain1.
>> Authentication was not working so on IIS web app in web.config in
>> system.web
>> I say identity impersonate="true" userName="domain1\username"
>> password="password" then it works fine -- but is this correct way to do?
>> I
>> don't like to have to have an account in there that has admin privs -- I
>> thought it should be just impersonate="true" and not have to send a
>> domain
>> username/password?
>> I read many things on nntp about this topic but was unable to finad
>> anything
>> to work except for the way I have it above.
>> Thank you!
>|||" I followed what Steve said and it worked great!"
Does this refer to using local reports, as was stated in your other
post?
I've been prototyping using the impersonation and it works, but I don't
know what the security requirement is eventually going to be. I don't
mind cutting the RS server out of the equation.
dev648237923 wrote:
> The Report Server is not exposed to the Internet -- only my web application
> can get at it -- more secure that way (so my IIS server is public but the
> SQL is not). I followed what Steve said and it worked great!
> Thanks.
> "sunil.jaikumar" <sunil.jaikumar@.gmail.com> wrote in message
> news:1152863352.300856.43580@.m73g2000cwd.googlegroups.com...
> > Why dont you enable anonymouse access and give everyone access in the
> > report server.
> >
> > dev648237923 wrote:
> >> I have two servers IIS Server and SQL2005.
> >> I have web app using ReportViewer on IIS Server to view reports on SQL
> >> Server SSRS.
> >> Both servers are on domain1.
> >>
> >> Authentication was not working so on IIS web app in web.config in
> >> system.web
> >> I say identity impersonate="true" userName="domain1\username"
> >> password="password" then it works fine -- but is this correct way to do?
> >> I
> >> don't like to have to have an account in there that has admin privs -- I
> >> thought it should be just impersonate="true" and not have to send a
> >> domain
> >> username/password?
> >>
> >> I read many things on nntp about this topic but was unable to finad
> >> anything
> >> to work except for the way I have it above.
> >>
> >> Thank you!
> >|||> Does this refer to using local reports, as was stated in your other
> post?
I followed what Steve said to get IIS authentication working to SSRS server.
I'm not using local Reports anymore (reason is that I need to be able to use
some of the features only available in Report Server -- see below for some
goo dlinks comparing).
Some links on Local vs Report Server:
http://msdn2.microsoft.com/en-us/library/ms251704.aspx
http://www.devx.com/dotnet/Article/30424/0/page/4|||Anonymous access seems like it would work but wait until you try to
administer RS. Since you are anonymous there is no such thing as
administrator rights. Oops. So then to administer it you have to switch off
of anonymous and then turn it back on. Most people would not want to do
that.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sunil.jaikumar" <sunil.jaikumar@.gmail.com> wrote in message
news:1152863352.300856.43580@.m73g2000cwd.googlegroups.com...
> Why dont you enable anonymouse access and give everyone access in the
> report server.
> dev648237923 wrote:
>> I have two servers IIS Server and SQL2005.
>> I have web app using ReportViewer on IIS Server to view reports on SQL
>> Server SSRS.
>> Both servers are on domain1.
>> Authentication was not working so on IIS web app in web.config in
>> system.web
>> I say identity impersonate="true" userName="domain1\username"
>> password="password" then it works fine -- but is this correct way to do?
>> I
>> don't like to have to have an account in there that has admin privs -- I
>> thought it should be just impersonate="true" and not have to send a
>> domain
>> username/password?
>> I read many things on nntp about this topic but was unable to finad
>> anything
>> to work except for the way I have it above.
>> Thank you!
>

authentication and deployment

We are in the process of converting all of our crystal reports to ssrs 2005.
We have out first report ready and wanted to go through the deployment from
"dev to test" and then "test to prod". The reports are all called via a web
application.
A few issues.
a. How do I deploy the report so that it will point to different databases
(dev, test, prod)
b. How do I get around having the login dialog box come up? The user has
already logged into the web app. We are not using Active Directory. We keep
login credentials in our own database.
Are there any good links to help me through these issues?
Thanks in advance.deploying the reports and access a different database is simple.
when you create your report, use a shared datasource.
after the deployment, you can change the connectionstring contain in this
shared datasource using the report manager interface
(http://localhost/reports)
The users are prompted for a login because, by default, RS use the windows
authentication to identify the user.
If you want to use your own security system with RS, you have to develop it
and this feature is available in the enterprise edition of RS only.
There is other options but these options depend on how you render your
reports to the end user.
do you use RS2005 + ASP.Net 2.0?
"dgator" <dgator@.discussions.microsoft.com> wrote in message
news:EE41CA2D-19BB-42EA-93F5-8721121185C7@.microsoft.com...
> We are in the process of converting all of our crystal reports to ssrs
> 2005.
> We have out first report ready and wanted to go through the deployment
> from
> "dev to test" and then "test to prod". The reports are all called via a
> web
> application.
> A few issues.
> a. How do I deploy the report so that it will point to different databases
> (dev, test, prod)
> b. How do I get around having the login dialog box come up? The user has
> already logged into the web app. We are not using Active Directory. We
> keep
> login credentials in our own database.
> Are there any good links to help me through these issues?
>
> Thanks in advance.|||yes, rs 2005 + asp.net 2.0.
I will look at the shared datasource, thanks.
Can you give me more information on using our own security?
Thanks
"Jéjé" wrote:
> deploying the reports and access a different database is simple.
> when you create your report, use a shared datasource.
> after the deployment, you can change the connectionstring contain in this
> shared datasource using the report manager interface
> (http://localhost/reports)
> The users are prompted for a login because, by default, RS use the windows
> authentication to identify the user.
> If you want to use your own security system with RS, you have to develop it
> and this feature is available in the enterprise edition of RS only.
> There is other options but these options depend on how you render your
> reports to the end user.
> do you use RS2005 + ASP.Net 2.0?
> "dgator" <dgator@.discussions.microsoft.com> wrote in message
> news:EE41CA2D-19BB-42EA-93F5-8721121185C7@.microsoft.com...
> > We are in the process of converting all of our crystal reports to ssrs
> > 2005.
> > We have out first report ready and wanted to go through the deployment
> > from
> > "dev to test" and then "test to prod". The reports are all called via a
> > web
> > application.
> >
> > A few issues.
> > a. How do I deploy the report so that it will point to different databases
> > (dev, test, prod)
> > b. How do I get around having the login dialog box come up? The user has
> > already logged into the web app. We are not using Active Directory. We
> > keep
> > login credentials in our own database.
> >
> > Are there any good links to help me through these issues?
> >
> >
> > Thanks in advance.
>
>|||Forms Authentication for Reporting Services
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
Andy Potter|||first, if you use ASP.Net 2.0, try to use the reportviewer webcontrol.
this control allows you to "control" the identity of the user when you
access report server.
so, your web site can use a specific authentication method (like form based)
and when you call your RS you'll use another identity (<identity
username=..." impersonate=true /> in the web.config)
Also...
You can give access to the anonymous user to your RS installation and setup
your datasource to ask for a login / password. this login / password can be
sent through the webcontrol without displaying this information to the end
user.
"dgator" <dgator@.discussions.microsoft.com> wrote in message
news:C4E0BD38-B30F-421C-BD4F-A331F9574C68@.microsoft.com...
> yes, rs 2005 + asp.net 2.0.
> I will look at the shared datasource, thanks.
> Can you give me more information on using our own security?
> Thanks
> "Jéjé" wrote:
>> deploying the reports and access a different database is simple.
>> when you create your report, use a shared datasource.
>> after the deployment, you can change the connectionstring contain in this
>> shared datasource using the report manager interface
>> (http://localhost/reports)
>> The users are prompted for a login because, by default, RS use the
>> windows
>> authentication to identify the user.
>> If you want to use your own security system with RS, you have to develop
>> it
>> and this feature is available in the enterprise edition of RS only.
>> There is other options but these options depend on how you render your
>> reports to the end user.
>> do you use RS2005 + ASP.Net 2.0?
>> "dgator" <dgator@.discussions.microsoft.com> wrote in message
>> news:EE41CA2D-19BB-42EA-93F5-8721121185C7@.microsoft.com...
>> > We are in the process of converting all of our crystal reports to ssrs
>> > 2005.
>> > We have out first report ready and wanted to go through the deployment
>> > from
>> > "dev to test" and then "test to prod". The reports are all called via
>> > a
>> > web
>> > application.
>> >
>> > A few issues.
>> > a. How do I deploy the report so that it will point to different
>> > databases
>> > (dev, test, prod)
>> > b. How do I get around having the login dialog box come up? The user
>> > has
>> > already logged into the web app. We are not using Active Directory.
>> > We
>> > keep
>> > login credentials in our own database.
>> >
>> > Are there any good links to help me through these issues?
>> >
>> >
>> > Thanks in advance.
>>|||Do all clients have to have 2.0 installed in order to use the reportviewer
control? I thought I had read this somewhere.
"Jéjé" wrote:
> first, if you use ASP.Net 2.0, try to use the reportviewer webcontrol.
> this control allows you to "control" the identity of the user when you
> access report server.
> so, your web site can use a specific authentication method (like form based)
> and when you call your RS you'll use another identity (<identity
> username=..." impersonate=true /> in the web.config)
> Also...
> You can give access to the anonymous user to your RS installation and setup
> your datasource to ask for a login / password. this login / password can be
> sent through the webcontrol without displaying this information to the end
> user.
>
> "dgator" <dgator@.discussions.microsoft.com> wrote in message
> news:C4E0BD38-B30F-421C-BD4F-A331F9574C68@.microsoft.com...
> > yes, rs 2005 + asp.net 2.0.
> >
> > I will look at the shared datasource, thanks.
> >
> > Can you give me more information on using our own security?
> >
> > Thanks
> >
> > "Jéjé" wrote:
> >
> >> deploying the reports and access a different database is simple.
> >> when you create your report, use a shared datasource.
> >> after the deployment, you can change the connectionstring contain in this
> >> shared datasource using the report manager interface
> >> (http://localhost/reports)
> >>
> >> The users are prompted for a login because, by default, RS use the
> >> windows
> >> authentication to identify the user.
> >> If you want to use your own security system with RS, you have to develop
> >> it
> >> and this feature is available in the enterprise edition of RS only.
> >> There is other options but these options depend on how you render your
> >> reports to the end user.
> >>
> >> do you use RS2005 + ASP.Net 2.0?
> >>
> >> "dgator" <dgator@.discussions.microsoft.com> wrote in message
> >> news:EE41CA2D-19BB-42EA-93F5-8721121185C7@.microsoft.com...
> >> > We are in the process of converting all of our crystal reports to ssrs
> >> > 2005.
> >> > We have out first report ready and wanted to go through the deployment
> >> > from
> >> > "dev to test" and then "test to prod". The reports are all called via
> >> > a
> >> > web
> >> > application.
> >> >
> >> > A few issues.
> >> > a. How do I deploy the report so that it will point to different
> >> > databases
> >> > (dev, test, prod)
> >> > b. How do I get around having the login dialog box come up? The user
> >> > has
> >> > already logged into the web app. We are not using Active Directory.
> >> > We
> >> > keep
> >> > login credentials in our own database.
> >> >
> >> > Are there any good links to help me through these issues?
> >> >
> >> >
> >> > Thanks in advance.
> >>
> >>
> >>
>
>|||no
its a web interface. nothing required on the client.
"dgator" <dgator@.discussions.microsoft.com> wrote in message
news:204EEB75-2A60-4B83-9702-0AD81DD9BC3B@.microsoft.com...
> Do all clients have to have 2.0 installed in order to use the reportviewer
> control? I thought I had read this somewhere.
> "Jéjé" wrote:
>> first, if you use ASP.Net 2.0, try to use the reportviewer webcontrol.
>> this control allows you to "control" the identity of the user when you
>> access report server.
>> so, your web site can use a specific authentication method (like form
>> based)
>> and when you call your RS you'll use another identity (<identity
>> username=..." impersonate=true /> in the web.config)
>> Also...
>> You can give access to the anonymous user to your RS installation and
>> setup
>> your datasource to ask for a login / password. this login / password can
>> be
>> sent through the webcontrol without displaying this information to the
>> end
>> user.
>>
>> "dgator" <dgator@.discussions.microsoft.com> wrote in message
>> news:C4E0BD38-B30F-421C-BD4F-A331F9574C68@.microsoft.com...
>> > yes, rs 2005 + asp.net 2.0.
>> >
>> > I will look at the shared datasource, thanks.
>> >
>> > Can you give me more information on using our own security?
>> >
>> > Thanks
>> >
>> > "Jéjé" wrote:
>> >
>> >> deploying the reports and access a different database is simple.
>> >> when you create your report, use a shared datasource.
>> >> after the deployment, you can change the connectionstring contain in
>> >> this
>> >> shared datasource using the report manager interface
>> >> (http://localhost/reports)
>> >>
>> >> The users are prompted for a login because, by default, RS use the
>> >> windows
>> >> authentication to identify the user.
>> >> If you want to use your own security system with RS, you have to
>> >> develop
>> >> it
>> >> and this feature is available in the enterprise edition of RS only.
>> >> There is other options but these options depend on how you render your
>> >> reports to the end user.
>> >>
>> >> do you use RS2005 + ASP.Net 2.0?
>> >>
>> >> "dgator" <dgator@.discussions.microsoft.com> wrote in message
>> >> news:EE41CA2D-19BB-42EA-93F5-8721121185C7@.microsoft.com...
>> >> > We are in the process of converting all of our crystal reports to
>> >> > ssrs
>> >> > 2005.
>> >> > We have out first report ready and wanted to go through the
>> >> > deployment
>> >> > from
>> >> > "dev to test" and then "test to prod". The reports are all called
>> >> > via
>> >> > a
>> >> > web
>> >> > application.
>> >> >
>> >> > A few issues.
>> >> > a. How do I deploy the report so that it will point to different
>> >> > databases
>> >> > (dev, test, prod)
>> >> > b. How do I get around having the login dialog box come up? The
>> >> > user
>> >> > has
>> >> > already logged into the web app. We are not using Active Directory.
>> >> > We
>> >> > keep
>> >> > login credentials in our own database.
>> >> >
>> >> > Are there any good links to help me through these issues?
>> >> >
>> >> >
>> >> > Thanks in advance.
>> >>
>> >>
>> >>
>>|||I believe that using the reportviewer is the way we should go, but I have yet
to see how to control the indentity of the user.
I have created a generic report user account on the report server machine
and want to use that for credentials. Becuase the user has already logged
into our app, we can trust them. I am not sure setting the impersonate tag
as it may affect the rest of the app in the wrong way. Not real sure here.
Can you please point me towards a good example of using the reportviewer
control with me passing my login credentials? For some reason, I'm not
getting this.
Thanks in advance.
"Jéjé" wrote:
> first, if you use ASP.Net 2.0, try to use the reportviewer webcontrol.
> this control allows you to "control" the identity of the user when you
> access report server.
> so, your web site can use a specific authentication method (like form based)
> and when you call your RS you'll use another identity (<identity
> username=..." impersonate=true /> in the web.config)
> Also...
> You can give access to the anonymous user to your RS installation and setup
> your datasource to ask for a login / password. this login / password can be
> sent through the webcontrol without displaying this information to the end
> user.
>
> "dgator" <dgator@.discussions.microsoft.com> wrote in message
> news:C4E0BD38-B30F-421C-BD4F-A331F9574C68@.microsoft.com...
> > yes, rs 2005 + asp.net 2.0.
> >
> > I will look at the shared datasource, thanks.
> >
> > Can you give me more information on using our own security?
> >
> > Thanks
> >
> > "Jéjé" wrote:
> >
> >> deploying the reports and access a different database is simple.
> >> when you create your report, use a shared datasource.
> >> after the deployment, you can change the connectionstring contain in this
> >> shared datasource using the report manager interface
> >> (http://localhost/reports)
> >>
> >> The users are prompted for a login because, by default, RS use the
> >> windows
> >> authentication to identify the user.
> >> If you want to use your own security system with RS, you have to develop
> >> it
> >> and this feature is available in the enterprise edition of RS only.
> >> There is other options but these options depend on how you render your
> >> reports to the end user.
> >>
> >> do you use RS2005 + ASP.Net 2.0?
> >>
> >> "dgator" <dgator@.discussions.microsoft.com> wrote in message
> >> news:EE41CA2D-19BB-42EA-93F5-8721121185C7@.microsoft.com...
> >> > We are in the process of converting all of our crystal reports to ssrs
> >> > 2005.
> >> > We have out first report ready and wanted to go through the deployment
> >> > from
> >> > "dev to test" and then "test to prod". The reports are all called via
> >> > a
> >> > web
> >> > application.
> >> >
> >> > A few issues.
> >> > a. How do I deploy the report so that it will point to different
> >> > databases
> >> > (dev, test, prod)
> >> > b. How do I get around having the login dialog box come up? The user
> >> > has
> >> > already logged into the web app. We are not using Active Directory.
> >> > We
> >> > keep
> >> > login credentials in our own database.
> >> >
> >> > Are there any good links to help me through these issues?
> >> >
> >> >
> >> > Thanks in advance.
> >>
> >>
> >>
>
>