Re: Persist impersonated NT credentials across pages

you can always cache the WindowsIdentity with System.Web.Cache....

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

Hello,

I am trying to build a web app that sits "on top" of SharePoint, but I
am having trouble with the Windows login. Here is what I want to
accomplish:

1. The user will log into my application using non-NT credentials
(stored in
DB).
2. My code then determines if this person is (for simplicity's sake) a
User
or Admin.
3. If a User, I want to log into the Windows domain using the SP_USER
domain
account.
4. If Admin, login using SP_ADMIN.
5. Then, I will link over to the SharePoint portal, having the SP_USER
or
SP_ADMIN credentials "automagically" passed.
I am having problems with steps 3 and 4. When you manually log into a
page using NT credentials--then link over to SharePoint--the Windows
credentials are automatically passed.

However, impersonated credentials fall out of context immediately
after that code block is finished executing. (The source code that I
used is similar to:
http://support.microsoft.com/default.aspx?scid=kb;en-us;306158.)

So my question, what API calls are needed to either:
- Store or otherwise persist the impersonated credentials to
out-of-context
pages
OR
- Programmatically perform a TRUE Windows domain login without user
intervention, so that credentails are automatically passed to another
page
without a Windows login prompt?
Thank you!

Eric



.

Relevant Pages

  • RE: synchronizing domain user Local cached credentials with domain
    ... Would you mind emailing me your script? ... windows taskbar bubble which would indicate that their password needs to be ... locally cached credentials are out of sync with domain credentials. ...
    (microsoft.public.windowsxp.security_admin)
  • Cached Password Issue???
    ... cannot browse the server. ... shares if I supply the same credentials however. ... Windows cannot query for the list of Group Policy ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with control hosted in IE
    ... The control is running on the client machine, so the default credentials are ... These will be the Windows logon from the ... > I logon to another machine using a local account (not one that the IIS ...
    (microsoft.public.dotnet.security)
  • WindowsTokenRoleProvider Anyone?
    ... Hey All, I'm attempting to put together a "secure" ASP.NET 2.0 application with one requirement that has given me a bit of grief: In a nutshell, if the user's session expires then they should be forced to re-authenticate with the application by providing logon credentials. ... the easy way to implement security with domain users is to use the Windows Authentication model built in to ASP.NET. ... to have the programmatic control over the authentication mechanism seems to leave only one choice in this scenario: ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Network isolation: local logins ?
    ... Regarding the local user accounts, in Windows XP and Windows 2003, if the ... secured/isolation network using its configured IPsec-based authentication ... The credentials of the user are not evaluated when determining ... IP extends the core IKE functionality of machine authentication to also ...
    (microsoft.public.windows.server.networking)