Can Developer and Evaluation Editions do web farms with custom authentication?

I am using the Report Manager in a web farm configuration with custom
authentication. It seems that neither the Developer nor the Evaluation
editions can work in this configuration, even though the descriptions for
these editions say that they're as capable as the Enterprise Edition (only
the licensing differs). The problem seems to be that the cookie generated by
the Report Server web service, when passed back from the browser, is being
rejected by the Report Manager. In a web farm, the domain name used to
access the Report Manager is different from that used by Report Manager to
access the Report Server web service. They can not be the same, and I think
because of this the cookie generated by Report Server is being rejected by
Report Manager.
I have tried SP1 and used the PassThroughCookie setting, but it still
doesn't work. Do I need to get the Enterprise Edition now when I am just in
development stage of this project?
Thanks.Dev and Eval should work with custom authentication as well as the
Enterprise SKU. I am not sure why the domain name for the cookie generated
by RS should be different than the domain report manager is in. BTW, you can
configure the RS cookie by changing settings in the <forms> tag in
Reportserver\web.config.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carlos C Tapang" <ctapang@.centerus.com> wrote in message
news:O$4fD4plEHA.2884@.TK2MSFTNGP09.phx.gbl...
> I am using the Report Manager in a web farm configuration with custom
> authentication. It seems that neither the Developer nor the Evaluation
> editions can work in this configuration, even though the descriptions for
> these editions say that they're as capable as the Enterprise Edition (only
> the licensing differs). The problem seems to be that the cookie generated
by
> the Report Server web service, when passed back from the browser, is being
> rejected by the Report Manager. In a web farm, the domain name used to
> access the Report Manager is different from that used by Report Manager to
> access the Report Server web service. They can not be the same, and I
think
> because of this the cookie generated by Report Server is being rejected by
> Report Manager.
> I have tried SP1 and used the PassThroughCookie setting, but it still
> doesn't work. Do I need to get the Enterprise Edition now when I am just
in
> development stage of this project?
> Thanks.
>|||Thank you for your response, Tudor. In the web farm I am working on, there
is a load balancer to which all requests go (one IP address, one domain
name). The load balancer then directs the request to a single web server in
the farm. Now, each web server has to have its own IP address, and this is
the IP address used by Report Manager to do a web service call to Report
Server. This internal IP address is different from the external IP address
made visible to the outside world by the load balancer. My suspicion is that
since the cookie was generated by the Report Server web service with the
internal IP address (which, by the way is also the RootServerUrl for the
service), when this same cookie is sent back from the browser, Report
Manager rejects it because now the browser is using the outside domain name
which is different from the internal IP address from which the cookie was
generated.
Is there an attribute within the <forms> element that can fix this problem?
I've looked and I have not seen any. How about <machineKey>, how can that
help me? Thanks very much again.
--Carlos
"Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
news:OwWho7rlEHA.896@.TK2MSFTNGP12.phx.gbl...
> Dev and Eval should work with custom authentication as well as the
> Enterprise SKU. I am not sure why the domain name for the cookie generated
> by RS should be different than the domain report manager is in. BTW, you
can
> configure the RS cookie by changing settings in the <forms> tag in
> Reportserver\web.config.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Carlos C Tapang" <ctapang@.centerus.com> wrote in message
> news:O$4fD4plEHA.2884@.TK2MSFTNGP09.phx.gbl...
> > I am using the Report Manager in a web farm configuration with custom
> > authentication. It seems that neither the Developer nor the Evaluation
> > editions can work in this configuration, even though the descriptions
for
> > these editions say that they're as capable as the Enterprise Edition
(only
> > the licensing differs). The problem seems to be that the cookie
generated
> by
> > the Report Server web service, when passed back from the browser, is
being
> > rejected by the Report Manager. In a web farm, the domain name used to
> > access the Report Manager is different from that used by Report Manager
to
> > access the Report Server web service. They can not be the same, and I
> think
> > because of this the cookie generated by Report Server is being rejected
by
> > Report Manager.
> >
> > I have tried SP1 and used the PassThroughCookie setting, but it still
> > doesn't work. Do I need to get the Enterprise Edition now when I am just
> in
> > development stage of this project?
> >
> > Thanks.
> >
> >
>|||I think you could use your internal name for the RM SOAP Url. You could then
set up the ReportSeverExternalURL, which is what your clients will see:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carlos C Tapang" <ctapang@.centerus.com> wrote in message
news:u83lLZslEHA.3608@.TK2MSFTNGP09.phx.gbl...
> Thank you for your response, Tudor. In the web farm I am working on, there
> is a load balancer to which all requests go (one IP address, one domain
> name). The load balancer then directs the request to a single web server
in
> the farm. Now, each web server has to have its own IP address, and this is
> the IP address used by Report Manager to do a web service call to Report
> Server. This internal IP address is different from the external IP address
> made visible to the outside world by the load balancer. My suspicion is
that
> since the cookie was generated by the Report Server web service with the
> internal IP address (which, by the way is also the RootServerUrl for the
> service), when this same cookie is sent back from the browser, Report
> Manager rejects it because now the browser is using the outside domain
name
> which is different from the internal IP address from which the cookie was
> generated.
> Is there an attribute within the <forms> element that can fix this
problem?
> I've looked and I have not seen any. How about <machineKey>, how can that
> help me? Thanks very much again.
> --Carlos
> "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> news:OwWho7rlEHA.896@.TK2MSFTNGP12.phx.gbl...
> > Dev and Eval should work with custom authentication as well as the
> > Enterprise SKU. I am not sure why the domain name for the cookie
generated
> > by RS should be different than the domain report manager is in. BTW, you
> can
> > configure the RS cookie by changing settings in the <forms> tag in
> > Reportserver\web.config.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Carlos C Tapang" <ctapang@.centerus.com> wrote in message
> > news:O$4fD4plEHA.2884@.TK2MSFTNGP09.phx.gbl...
> > > I am using the Report Manager in a web farm configuration with custom
> > > authentication. It seems that neither the Developer nor the Evaluation
> > > editions can work in this configuration, even though the descriptions
> for
> > > these editions say that they're as capable as the Enterprise Edition
> (only
> > > the licensing differs). The problem seems to be that the cookie
> generated
> > by
> > > the Report Server web service, when passed back from the browser, is
> being
> > > rejected by the Report Manager. In a web farm, the domain name used to
> > > access the Report Manager is different from that used by Report
Manager
> to
> > > access the Report Server web service. They can not be the same, and I
> > think
> > > because of this the cookie generated by Report Server is being
rejected
> by
> > > Report Manager.
> > >
> > > I have tried SP1 and used the PassThroughCookie setting, but it still
> > > doesn't work. Do I need to get the Enterprise Edition now when I am
just
> > in
> > > development stage of this project?
> > >
> > > Thanks.
> > >
> > >
> >
> >
>|||Thanks again. I've read this and have tried setting ReportServerExternalUrl,
but it didn't seem to have any effect. I read the section of RS
documentation that you referred to below again, and determined that may be
my installation does not recognize that it is in a web farm. You see, in our
development environment, we are starting off with just one server, although
there is a load balancer that routes packets from the client to this one
server. So this RS server has its own NETBIOS machine name and IP address
separate and different from that of the load balancer. The client has no
access to the RS server NETBIOS machine name and IP address; it can only
access it through the load balancer. However, like I already said, we are
starting off with just one RS server.
The instructions for instalation in a web farm assume two or more servers,
and it seems that it is the presence of the second server that determines
the behavior of RS. In other words, if there is no second server, RS does
not behave like a web farm component. Is this true?
Also, how does RS deal with custom authentication in a web farm? Will RM
accept cookies generated by the Report Service web service on another domain
(ReportServerUrl should point to the same server in a web farm, which is
different for each server, and different from the main website URL). In
other words, has Microsoft tested RS in a web farm with custom
authentication?
--Carlos
"Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
news:uSJPzremEHA.3372@.TK2MSFTNGP15.phx.gbl...
> I think you could use your internal name for the RM SOAP Url. You could
then
> set up the ReportSeverExternalURL, which is what your clients will see:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp
>
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Carlos C Tapang" <ctapang@.centerus.com> wrote in message
> news:u83lLZslEHA.3608@.TK2MSFTNGP09.phx.gbl...
> > Thank you for your response, Tudor. In the web farm I am working on,
there
> > is a load balancer to which all requests go (one IP address, one domain
> > name). The load balancer then directs the request to a single web server
> in
> > the farm. Now, each web server has to have its own IP address, and this
is
> > the IP address used by Report Manager to do a web service call to Report
> > Server. This internal IP address is different from the external IP
address
> > made visible to the outside world by the load balancer. My suspicion is
> that
> > since the cookie was generated by the Report Server web service with the
> > internal IP address (which, by the way is also the RootServerUrl for the
> > service), when this same cookie is sent back from the browser, Report
> > Manager rejects it because now the browser is using the outside domain
> name
> > which is different from the internal IP address from which the cookie
was
> > generated.
> >
> > Is there an attribute within the <forms> element that can fix this
> problem?
> > I've looked and I have not seen any. How about <machineKey>, how can
that
> > help me? Thanks very much again.
> >
> > --Carlos
> >
> > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > news:OwWho7rlEHA.896@.TK2MSFTNGP12.phx.gbl...
> > > Dev and Eval should work with custom authentication as well as the
> > > Enterprise SKU. I am not sure why the domain name for the cookie
> generated
> > > by RS should be different than the domain report manager is in. BTW,
you
> > can
> > > configure the RS cookie by changing settings in the <forms> tag in
> > > Reportserver\web.config.
> > >
> > > --
> > > Tudor Trufinescu
> > > Dev Lead
> > > Sql Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > >
> > > "Carlos C Tapang" <ctapang@.centerus.com> wrote in message
> > > news:O$4fD4plEHA.2884@.TK2MSFTNGP09.phx.gbl...
> > > > I am using the Report Manager in a web farm configuration with
custom
> > > > authentication. It seems that neither the Developer nor the
Evaluation
> > > > editions can work in this configuration, even though the
descriptions
> > for
> > > > these editions say that they're as capable as the Enterprise Edition
> > (only
> > > > the licensing differs). The problem seems to be that the cookie
> > generated
> > > by
> > > > the Report Server web service, when passed back from the browser, is
> > being
> > > > rejected by the Report Manager. In a web farm, the domain name used
to
> > > > access the Report Manager is different from that used by Report
> Manager
> > to
> > > > access the Report Server web service. They can not be the same, and
I
> > > think
> > > > because of this the cookie generated by Report Server is being
> rejected
> > by
> > > > Report Manager.
> > > >
> > > > I have tried SP1 and used the PassThroughCookie setting, but it
still
> > > > doesn't work. Do I need to get the Enterprise Edition now when I am
> just
> > > in
> > > > development stage of this project?
> > > >
> > > > Thanks.
> > > >
> > > >
> > >
> > >
> >
> >
>