Using SharePoint it’s easy to run a block of code with elevated permissions:<\/p>\n
\r\nSPSecurity.RunWithElevatedPrivileges(()=>\r\n{\r\n using (SPSite elevatedSite = new SPSite(siteId))\r\n {\r\n using (SPWeb elevatedWeb = elevatedSite.OpenWeb(wedId))\r\n {\r\n \/\/ operations using elevated SPWeb object...\r\n }\r\n }\r\n});\r\n<\/pre>\nThis is fine for SharePoint related impersonations. Any code executed within the elevated block that authenticates using an object instantiated outside the RunWithElevatedPrivileges<\/em> block will run using the context of the current user and not the elevated account. So for example, if you wanted to make a web method call using a single user (or connect to a database) and not the current context, the following code block will achieve this for you:
\n<\/p>\n\r\nusing (WindowsImpersonationContext context = WindowsIdentity.Impersonate(System.IntPtr.Zero))\r\n{\r\n try\r\n {\r\n \/\/ code to run under the context of the current application pool identity.\r\n\r\n }\r\n catch (Exception ex)\r\n {\r\n \/\/ error loging, etc.\r\n throw;\r\n }\r\n finally\r\n {\r\n context.Undo();\r\n }\r\n}\r\n<\/pre>\nOf course, within SharePoint, if you want a set of processes to run under the context of a specific user, it would be better to contain the code within a service application (for example) which will run under the context of the defined managed account and not the current user context.<\/p>\n","protected":false},"excerpt":{"rendered":"
Using SharePoint it’s easy to run a block of code with elevated permissions: SPSecurity.RunWithElevatedPrivileges(()=> { using (SPSite elevatedSite = new SPSite(siteId)) { using (SPWeb elevatedWeb = elevatedSite.OpenWeb(wedId)) { \/\/ operations using elevated SPWeb object… } } }); This is fine … Continue reading