December 3, 2009 at 9:08 am
We are currently trying to get a web application to run that uses ASP.NET to server up reports from the reportserver. We have added AZMAN to the application to validate access to certain reports. The problem comes from the security. If AZMAN is disabled, the user is able to run the reports from the application. However, once AZMAN is enabled, the user logon is changed to ANONYMOUS LOGON to SQL SERVER. Does anyone know how to counter this loss of user context?
December 3, 2009 at 10:21 am
rich.brown (12/3/2009)
We are currently trying to get a web application to run that uses ASP.NET to server up reports from the reportserver. We have added AZMAN to the application to validate access to certain reports. The problem comes from the security. If AZMAN is disabled, the user is able to run the reports from the application. However, once AZMAN is enabled, the user logon is changed to ANONYMOUS LOGON to SQL SERVER. Does anyone know how to counter this loss of user context?
You need to write a lot of code to get AZMAN to talk to Asp.net simpler solution is to use Asp.net AD provider which works with SQL Server in all context because AD provider uses either LDAP or IIS to resolve the users before talking to your network AD.
Asp.net have instructions to resolve users to LDAP, IIS and RDBMS not AD because AD primary task is to authenticate users to local network and manage ACL (access control list).
We have added AZMAN to the application to validate access to certain reports
All you actually need is authorization sections in your SSRS Web.Config because it uses Windows Authentication so you can use ACL (access control list) to control access to SSRS folders.
Kind regards,
Gift Peddie
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply