Forms authentication and URL access

Ive written a security extension based on microsoft samples, i can call the
SOAP API and get authenticated but i dont know what to do so i can use this
authentication method using URL access, i need that since i want to be able
to keep the toolbar.Rodrigo,
The typical integration scenario for Forms Autnentication and web-based URL
reporting is:
1. You have a web app which authenticates the user on the server side.
2. The web app calls LogonUser SOAP API.
3. The web app utilizes the Report Viewer or another approach (static
hyperlinks, client-side javascript, etc) to submit URL-based report
requests.
So, once the user is authenticated the we app just needs to submit report
requests on the client side of the application. As long as the
authentication ticket (cookie) is passed successfully, the reports should
render fine subject to aurhorization restrictions.
Hope this helps.
----
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
----
"Rodrigo Sánchez" <rodrigoss@.netshoreprogramming.com> wrote in message
news:%23p%23QEV5jEHA.704@.TK2MSFTNGP09.phx.gbl...
> Ive written a security extension based on microsoft samples, i can call
the
> SOAP API and get authenticated but i dont know what to do so i can use
this
> authentication method using URL access, i need that since i want to be
able
> to keep the toolbar.
>|||thanks, ill review my implementation and get back to you with more detail if
needed
"Teo Lachev" <teo.lachev@.nospam.prologika.com> escribió en el mensaje
news:%23rrIi15jEHA.592@.TK2MSFTNGP11.phx.gbl...
> Rodrigo,
> The typical integration scenario for Forms Autnentication and web-based
URL
> reporting is:
> 1. You have a web app which authenticates the user on the server side.
> 2. The web app calls LogonUser SOAP API.
> 3. The web app utilizes the Report Viewer or another approach (static
> hyperlinks, client-side javascript, etc) to submit URL-based report
> requests.
> So, once the user is authenticated the we app just needs to submit report
> requests on the client side of the application. As long as the
> authentication ticket (cookie) is passed successfully, the reports should
> render fine subject to aurhorization restrictions.
>
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ----
> "Rodrigo Sánchez" <rodrigoss@.netshoreprogramming.com> wrote in message
> news:%23p%23QEV5jEHA.704@.TK2MSFTNGP09.phx.gbl...
> > Ive written a security extension based on microsoft samples, i can call
> the
> > SOAP API and get authenticated but i dont know what to do so i can use
> this
> > authentication method using URL access, i need that since i want to be
> able
> > to keep the toolbar.
> >
> >
>|||Teo - Is it a requirement of Forms Authentication that the users who are
authenticated to the ASP.NET web app have credentials defined in reporting
services? If not, how can you manage that user's rights?
thanks
"Teo Lachev" wrote:
> Rodrigo,
> The typical integration scenario for Forms Autnentication and web-based URL
> reporting is:
> 1. You have a web app which authenticates the user on the server side.
> 2. The web app calls LogonUser SOAP API.
> 3. The web app utilizes the Report Viewer or another approach (static
> hyperlinks, client-side javascript, etc) to submit URL-based report
> requests.
> So, once the user is authenticated the we app just needs to submit report
> requests on the client side of the application. As long as the
> authentication ticket (cookie) is passed successfully, the reports should
> render fine subject to aurhorization restrictions.
>
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ----
> "Rodrigo Sánchez" <rodrigoss@.netshoreprogramming.com> wrote in message
> news:%23p%23QEV5jEHA.704@.TK2MSFTNGP09.phx.gbl...
> > Ive written a security extension based on microsoft samples, i can call
> the
> > SOAP API and get authenticated but i dont know what to do so i can use
> this
> > authentication method using URL access, i need that since i want to be
> able
> > to keep the toolbar.
> >
> >
>
>|||No credentials, just security policies in the report catalog. You would
typically use the Report Manager to set up your user security policy just
like you would normally do with Windows authentication.
Please note though that you don't have to register invividual users.
Instead, if it makes sense, you can group users into application-defined
roles outside of the Report Server. Then, in the Report Manager you will set
up security policies based the roles not users for easier maintainance.
Finally, in your CheckAccess overloads you need to take extra steps to find
out which role the user belongs to and authorize the user based on the user
role membership
Does this confuse even more :-)
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
news:9ABD45EE-390D-4272-A0AC-119114A0638E@.microsoft.com...
> Teo - Is it a requirement of Forms Authentication that the users who are
> authenticated to the ASP.NET web app have credentials defined in reporting
> services? If not, how can you manage that user's rights?
> thanks
> "Teo Lachev" wrote:
> > Rodrigo,
> >
> > The typical integration scenario for Forms Autnentication and web-based
URL
> > reporting is:
> > 1. You have a web app which authenticates the user on the server side.
> > 2. The web app calls LogonUser SOAP API.
> > 3. The web app utilizes the Report Viewer or another approach (static
> > hyperlinks, client-side javascript, etc) to submit URL-based report
> > requests.
> >
> > So, once the user is authenticated the we app just needs to submit
report
> > requests on the client side of the application. As long as the
> > authentication ticket (cookie) is passed successfully, the reports
should
> > render fine subject to aurhorization restrictions.
> >
> >
> >
> > --
> > Hope this helps.
> >
> > ----
> > Teo Lachev, MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > Publisher website: http://www.manning.com/lachev
> > Buy it from Amazon.com: http://shrinkster.com/eq
> > Home page and blog: http://www.prologika.com/
> > ----
> >
> > "Rodrigo Sánchez" <rodrigoss@.netshoreprogramming.com> wrote in message
> > news:%23p%23QEV5jEHA.704@.TK2MSFTNGP09.phx.gbl...
> > > Ive written a security extension based on microsoft samples, i can
call
> > the
> > > SOAP API and get authenticated but i dont know what to do so i can use
> > this
> > > authentication method using URL access, i need that since i want to be
> > able
> > > to keep the toolbar.
> > >
> > >
> >
> >
> >