Ask for debugging when customize authorization in the security extension sample of report server

Question

I have tried the sample of reporting service provide in MSDN
http://msdn.microsoft.com/en-us/library/ms160724.aspx
I successfully deploy the sample in my report server. But I want to know what happen in the authorization in order to authorize right to different user login from the login page. I can't debug the class Authorization by attaching aspnet_wp.exe in the process.
Actually I want to know the value of secDesc, AceStruct ace in each CheckAccess method. But I can't debug in the file Authorization that implement interface IAuthorizationExtension. I try to add some coding in the Authorization class to write  the value of secDesc, AceStruct ace in file. It fails. Create Event log.... it also fail...any other method?

Answer 1

Hi,
"secDesc" is the security descriptor, which contains the following information for an item in the report server database:
The group or user that has some type of permission to perform operations on the item.
The item's type.
A discretionary access control list controlling access to the item.
AceStruct  is an access control entry for a trustee (user, group, or computer) that specifies the operations that a trustee can perform on items in the report server database. You can get a instance of AceStruct by de-serializing “secDesc”
In addition, when you tried to debug the program, did you follow the steps below.
Start Visual Studio .NET and open CustomSecurity.sln on your test report server.
Open Internet Explorer and navigate to Report Manager while leaving the sample code open in Visual Studio.
Switch to Visual Studio and set some break points in the custom security extension project code.
With the extension project still the active window, from the Debug menu, click Process.The Processes dialog opens.
From the list of processes, select the Aspnet_wp.exe process (or W3wp.exe, if your application is deployed on IIS 6.0), and click Attach.
In the Attach to Process dialog, select the Common Language Runtime program type, and then click OK. For improved debugging performance, make sure that Native is not a selected program type.
When the sample runs, a logon form appears. Type the user credentials into the logon form and click the Logon button. Whenever your break points are encountered during processing, the debugger should stop execution that point.
Step through your code using the F11 key.
Hope this helps.
Thanks.