Authentication with AD and cookies

Hi all!
We are going to set up Reporting Services 2005. We have two groups of
customers that are going to access our reports; internal and external
customers.
The internal customers should be authenticated through Active Directory,
while the external customers should be authenticated using cookies. The
external customers will first logon to another web-application which has its
own user database. From this application they will have a link to Reporting
Services.
How will I have to set up my reporting services server(s) to achieve this?
The internal and external uses are not going to share reports. However, the
extenal users should access linked reports (ie. same report but different
parameter values).
Thanks in advance for your help.RS doesn't support a mixed security mode, so it has to be either Windows or
custom security. It looks like in your scenario, Windows security could be a
better fit. Assuming that you don't need the external customer identity in
your reports, once the web app authenticates the external customers, it can
connect to RS using a single trusted account, e.g. the identity of the IIS
application pool in Windows Server 2003.
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"Billy" <Billy@.discussions.microsoft.com> wrote in message
news:8CBE5F6F-B2A5-44DA-A8DA-E4887C60BF67@.microsoft.com...
> Hi all!
> We are going to set up Reporting Services 2005. We have two groups of
> customers that are going to access our reports; internal and external
> customers.
> The internal customers should be authenticated through Active Directory,
> while the external customers should be authenticated using cookies. The
> external customers will first logon to another web-application which has
> its
> own user database. From this application they will have a link to
> Reporting
> Services.
> How will I have to set up my reporting services server(s) to achieve this?
> The internal and external uses are not going to share reports. However,
> the
> extenal users should access linked reports (ie. same report but different
> parameter values).
> Thanks in advance for your help.
>|||ok.
Is it possible to set up two separate instances of RS om the same server and
then route external users to instance A and internal users to instance B?
"Teo Lachev [MVP]" wrote:
> RS doesn't support a mixed security mode, so it has to be either Windows or
> custom security. It looks like in your scenario, Windows security could be a
> better fit. Assuming that you don't need the external customer identity in
> your reports, once the web app authenticates the external customers, it can
> connect to RS using a single trusted account, e.g. the identity of the IIS
> application pool in Windows Server 2003.
> --
> HTH,
> ---
> Teo Lachev, MVP, MCSD, MCT
> "Microsoft Reporting Services in Action"
> "Applied Microsoft Analysis Services 2005"
> Home page and blog: http://www.prologika.com/
> ---
> "Billy" <Billy@.discussions.microsoft.com> wrote in message
> news:8CBE5F6F-B2A5-44DA-A8DA-E4887C60BF67@.microsoft.com...
> > Hi all!
> >
> > We are going to set up Reporting Services 2005. We have two groups of
> > customers that are going to access our reports; internal and external
> > customers.
> >
> > The internal customers should be authenticated through Active Directory,
> > while the external customers should be authenticated using cookies. The
> > external customers will first logon to another web-application which has
> > its
> > own user database. From this application they will have a link to
> > Reporting
> > Services.
> >
> > How will I have to set up my reporting services server(s) to achieve this?
> > The internal and external uses are not going to share reports. However,
> > the
> > extenal users should access linked reports (ie. same report but different
> > parameter values).
> >
> > Thanks in advance for your help.
> >
>
>|||I don't think this scenario is officially supported but it looks like when
there is a will, there is a way
(http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk).
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"Billy" <Billy@.discussions.microsoft.com> wrote in message
news:E6DD5D19-8C25-4C1E-8154-5C736723D80C@.microsoft.com...
> ok.
> Is it possible to set up two separate instances of RS om the same server
> and
> then route external users to instance A and internal users to instance B?
> "Teo Lachev [MVP]" wrote:
>> RS doesn't support a mixed security mode, so it has to be either Windows
>> or
>> custom security. It looks like in your scenario, Windows security could
>> be a
>> better fit. Assuming that you don't need the external customer identity
>> in
>> your reports, once the web app authenticates the external customers, it
>> can
>> connect to RS using a single trusted account, e.g. the identity of the
>> IIS
>> application pool in Windows Server 2003.
>> --
>> HTH,
>> ---
>> Teo Lachev, MVP, MCSD, MCT
>> "Microsoft Reporting Services in Action"
>> "Applied Microsoft Analysis Services 2005"
>> Home page and blog: http://www.prologika.com/
>> ---
>> "Billy" <Billy@.discussions.microsoft.com> wrote in message
>> news:8CBE5F6F-B2A5-44DA-A8DA-E4887C60BF67@.microsoft.com...
>> > Hi all!
>> >
>> > We are going to set up Reporting Services 2005. We have two groups of
>> > customers that are going to access our reports; internal and external
>> > customers.
>> >
>> > The internal customers should be authenticated through Active
>> > Directory,
>> > while the external customers should be authenticated using cookies. The
>> > external customers will first logon to another web-application which
>> > has
>> > its
>> > own user database. From this application they will have a link to
>> > Reporting
>> > Services.
>> >
>> > How will I have to set up my reporting services server(s) to achieve
>> > this?
>> > The internal and external uses are not going to share reports. However,
>> > the
>> > extenal users should access linked reports (ie. same report but
>> > different
>> > parameter values).
>> >
>> > Thanks in advance for your help.
>> >
>>