in

Prologika Forums

Business Intelligence to the Masses
Latest post 05-27-2008 12:27 PM by tlachev. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 05-23-2008 4:51 PM

    • vkv
    • Top 10 Contributor
    • Joined on 06-19-2006
    • Posts 88

    Unauthorized error for report viewer remote mode reports

    Hi Teo

     I have a asp.net windows authenticated application.In application i have report viewer which points to remote mode report server reports.when i run the report in local i can see report in report viewer,when i deploy the report to server and i ran from it report viewer is displaying "The request failed with HTTP status 401: Unauthorized".

    I am understanding why it is unauthorized.

    In web config i did identitiy imeprsonate to true.

    Can you please let me know the solution.

    Thanks

    vkv

  • 05-24-2008 5:33 PM In reply to

    Re: Unauthorized error for report viewer remote mode reports

    If the ASP.NET application and the report server are hosted on two separate servers, you need more than impersonation. You need delegation because your web server needs to delegate the user credentials to the second machine. This can be accomplished by configuring Kerberos.

  • 05-27-2008 12:03 PM In reply to

    • vkv
    • Top 10 Contributor
    • Joined on 06-19-2006
    • Posts 88

    Re: Unauthorized error for report viewer remote mode reports

    Hi Teo,

     Thanks for reply.Is there any other method?Kerberos requires some changes in Active directory which is impossible in our organization to touch for developers.

    Thanks

    Vamsi

  • 05-27-2008 12:27 PM In reply to

    Re: Unauthorized error for report viewer remote mode reports

    Do you need the report server to know who the user is, such as to set up role-based security based on the user identity? If not, you can use the trusted subsystem approach I described in the book. If you need to pass the user identity without kerberos and you know the user password, you can impersonate the user, as discussed here.

    As a side note, Kerberos may not require all that many changes to AD but I agree that you need admin rights to make them which could be an issue.

Page 1 of 1 (4 items)
Copyright © 2005 Prologika, LLC
Powered by Community Server (Commercial Edition), by Telligent Systems