Impersonation problem in Sharepoint 2007
- From: jerome.decouenne@xxxxxxxxx
- Date: 28 Jul 2006 10:54:15 -0700
Hello,
It's been four days that we are looking for something to help us, but
we're still having problems getting it to work.
The thing we are trying to do is to grant temporarly rights to the
connected user, in order to use a Sharepoint method that demand
administrator privileges, such as create SPWebs, SPLists and
SPListItems or retrieve the WelcomePage of a SPWeb.
The first thing we thought is the classical Impersonate method, used in
SPS 2003. But it doesn't work!
We thought then, that it was the problem of the "Roles retrieval" in
SPS 2003, which forces to use AppDomains. But this solution is not
suitable because everything we try causes an Access Denied Exception.
There must be anything else.
When we impersonate, the WindowsIdendity associated to the context
correctly becomes the AppPool Identity (checked with Debug). But it
seems that the security context on which MOSS is based, is still the
user's one (checked by using its API : for example,
SPContext.Current.Web.CurrentUser is a SPUser
corresponding to the one is connected). This seems to have for
consequences that even in a impersonated block, if we create a new
list, the creator of the list is the logon user, not the current user
of the HttpContext!
Has anyone gotten this to work? Am I forgetting something?
Thanks for your reply
Jérôme D.
.
- Follow-Ups:
- Re: Impersonation problem in Sharepoint 2007
- From: jerome . decouenne
- Re: Impersonation problem in Sharepoint 2007
- Prev by Date: The specified program requires a newer version of Windows.
- Next by Date: Re: save a subsite as template
- Previous by thread: The specified program requires a newer version of Windows.
- Next by thread: Re: Impersonation problem in Sharepoint 2007
- Index(es):
Relevant Pages
|