MSDN Magazine - September 2008 - (Page 49)

Figure 3 SiteActionsCustomSubMenu public class SiteActionsCustomSubMenu : WebControl { protected override void OnLoad(EventArgs e) { this.EnsureChildControls(); base.OnLoad(e); } protected override void CreateChildControls() { SPSite siteCollection = SPContext.Current.Site; SPWeb site = SPContext.Current.Web; SPUser user = site.CurrentUser; // provide security trimming if (IsCurrentUserInGroup("Auditors") || IsCurrentUserInGroup("Audit Managers") || user.IsSiteAdmin) { string siteCollectionPath = siteCollection.Url; if (!siteCollectionPath.EndsWith(@"/")) siteCollectionPath += "/"; SubMenuTemplate smt = new SubMenuTemplate(); smt.Text = "Auditing Support"; smt.ID = "mnuAuditingSupport"; smt.Description = "Configure and View Auditing"; smt.ImageUrl = siteCollectionPath + @"_layouts/images/AuditingDemo/AfricanPith32.gif"; smt.Sequence = 400; MenuItemTemplate mit1 = new MenuItemTemplate(); mit1.ID = "mnuAuditLog"; mit1.Text = "Audit Log"; mit1.Description = "Inspect Audit Entries"; mit1.Sequence = 401; mit1.ClientOnClickNavigateUrl = siteCollectionPath + "_layouts/AuditingDemo/AuditLogViewer.aspx"; } mit1.ImageUrl = siteCollectionPath + @"_layouts/images/AuditingDemo/Binoculars32.gif"; // add menu item to Controls collection smt.Controls.Add(mit1); // perform extra security trimming for menu for AuditConfig.aspx if (IsCurrentUserInGroup("Audit Managers") || user.IsSiteAdmin) { MenuItemTemplate mit2 = new MenuItemTemplate(); mit2.ID = "mnuAuditingConfiguration"; mit2.Text = "Auditing Configuration"; mit2.Description = "Enable/Disable Auditing"; mit2.Sequence = 402; mit2.ClientOnClickNavigateUrl = siteCollectionPath + "_layouts/AuditingDemo/AuditConfig.aspx"; mit2.ImageUrl = siteCollectionPath + @"_layouts/images/AuditingDemo/Compass32.gif"; smt.Controls.Add(mit2); } this.Controls.Add(smt); } } private bool IsCurrentUserInGroup(string GroupName) { SPWeb site = SPContext.Current.Web; foreach (SPGroup group in site.SiteGroups) { if (group.Name.Equals(GroupName)) { return group.ContainsCurrentUser; } } throw new ApplicationException("There is no group named " + GroupName); } propriate elements into the manifest.xml file, and, as a result, the required SafeControl entry is automatically added to one or more web.config files whenever the AuditingDemo.wsp solution package is deployed within a farm. The AuditingDemo solution provides the AuditLogViewer.aspx custom application page shown in Figure 4. This page provides the users with a view of all the audit entries for the entire site col- Viewing Audit Log Entries lection. There is also a button on this page with the caption Clear Audit Log. This button is security trimmed so it is only shown to site-collection owners. The code behind this button deletes all entries from the audit log, which you might find to be helpful while testing a custom auditing solution. The code behind AuditLogViewer.aspx uses an SPAuditQuery object to query the audit log of the current site collection. A query is run by calling the GetEntries method on the Audit property of an SPSite object. A call to GetEntries returns an SPAuditEntryCollection object that can be enumerated to inspect each audit entry as an SPAuditEntry object: SPSite SiteCollection = SPContext.Current.Site; SPAuditQuery wssQuery = new SPAuditQuery(SiteCollection); SPAuditEntryCollection auditCol = SiteCollection.Audit.GetEntries(wssQuery); foreach (SPAuditEntry entry in auditCol) { // enumererate through each audit entry } Figure 4 AuditLogViewer.aspx Displays Audit Log Entries msdnmagazine.com There are many ways in which you can enumerate through an SPAuditEntryCollection to create a display. I used a technique where I dynamically create an ADO.NET DataTable object and then populate it with one row of information per audit entry. By creating a DataTable, it becomes relatively simple to display the audit information by binding it to an SPGridView control. The code behind the AuditLogViewer.aspx page must deal with a special security concern. If you examine the code that queries the audit log, you will see that it first makes a call to RunWithElevatedPrivileges so that it can run under the identity of the privileged September 2008 49 http://msdnmagazine.com

Table of Contents Feed for the Digital Edition of MSDN Magazine - September 2008

MSDN Magazine - September 2008 Contents Toolbox CLR Inside Out Data Points Advanced Basics Office Space Cutting Edge Hierarchy ID New Features for Microsoft SQL Server 2008 Prism Data Services Advanced WPF Test Run Security Briefs Foundations { End Bracket }

MSDN Magazine - September 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.