WEB FORM --> DOMAIN USER AUTHENTICATION

Ask a Question related to ASP.NET Security, Design and Development.

  1. #1

    Default WEB FORM --> DOMAIN USER AUTHENTICATION

    Microsoft Knowledge Base Article - 306158
    [[url]http://support.microsoft.com/default.aspx?scid=kb;en-[/url]
    us;306158] shows a method to impersonate a specific user
    in code via a web form.

    The trouble is that the impersonation isn't being
    persisted accost the web application. Once the user moves
    onto the next page they are back in the NT
    AUTHORITY\SYSTEM security context.

    The desired scenario is:
    1.) The user must enter there DOMAIN account username &
    password into a WEB FORM (can't have the network logon
    prompt popup).

    2.) The application must run in this users security
    context as long as they are 'IN' the application. So every
    page the user accesses within the application runs under
    their security context.

    ----------------------------------------------
    Subject: RE: Domain Authentication via Web Form -
    PERSISTANCE?
    From: "Wei-Dong Xu [MSFT]" <v-wdxu@online.microsoft.com>
    Sent: 8/7/2003 7:44:58 PM

    Hi Ty,

    In IIS6, if you choose the IIS6 worker process isolcation
    mode(WPIM) to run
    asp.net, the asp.net web application will run in a worker
    process and the
    application will decide how to impersonate the process. If
    you select the
    IIS5 isolation mode to execute the asp.net application,
    the application
    will run in aspnet process. The applicaiton will decide
    his own entity as
    well.

    It appears that this is a ASP.net develop issue, not IIS.
    To better serve
    you, the Asp.net support team has created a aspnet
    newsgroup for you. I
    think these asp.net experts will help you a lot on this
    issue. Please go to:
    Microsoft.public.dotnet.framework.aspnet

    Does this answer your question? Thank you for using
    Microsoft NewsGroup!

    Wei-Dong Xu
    Microsoft Product Support Services
    Get Secure! - [url]www.microsoft.com/security[/url]
    This posting is provided "AS IS" with no warranties, and
    confers no rights."
    ----------------------------------------------

    Ty Millwee Guest

  2. Similar Questions and Discussions

    1. Problem creating a new user with form authentication enabled
      Hi I have implemented form authentication with login.aspx as the form to call if the user is not authenticated using the following in the...
    2. How to determine if a user (integrated authentication) is part of a domain security group.
      I am trying to determine from an ASP.NET 1.1 page if a user is a member of a Global Security group (Windows 2000). When I check...
    3. Q: User Control & Form Authentication
      Hi, I have a page (home.aspx) and an user control (footer.ascx) which located in different websites. The website that user control located...
    4. How to permit Domain User in AD domain install software on his/her machine?
      Hello, I have AD domain and 100 users, 15 of them are developers. Developers need full control over their machines. They need to install...
    5. Domain Login - One User Can/Another User Cannot from same Win XP computer
      Okay ... I'm confused. I installed a brand new computer and everything was working fine. I was then advised who would be getting the computer,...
  3. #2

    Default RE: WEB FORM --> DOMAIN USER AUTHENTICATION

    Hello Ty,

    Thanks for posting in the group.

    The KB article that you mentioned introduces some methods for impersonation in asp.net. If we want to enable asp.net
    impersonation in the whole web app, we need to set it in web.config file. Coding it in a web form only enables it in this web
    page.

    After reviewing your post, I think what you need is a login page and logout page and you want to associate uses with domain
    users. If so, I think you need to use form authentication method in the web application. Please refer to:
    "Building Secure ASP.NET Applications: Authentication, Authorization, and Secure Communication"
    [url]http://msdn.microsoft.com/vcsharp/downloads/samples/default.aspx?pull=/library/en-us/dnnetsec/html/secnetht02.asp[/url]

    Hope that helps.

    Best regards,
    Yanhong Huang
    Microsoft Online Partner Support

    Get Secure! - [url]www.microsoft.com/security[/url]
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    !Content-Class: urn:content-classes:message
    !From: "Ty Millwee" <tmillwee@arclightsystems.com>
    !Sender: "Ty Millwee" <tmillwee@arclightsystems.com>
    !Subject: WEB FORM --> DOMAIN USER AUTHENTICATION
    !Date: Fri, 8 Aug 2003 12:38:39 -0700
    !Lines: 58
    !Message-ID: <01e801c35de4$aa87a990$a401280a@phx.gbl>
    !MIME-Version: 1.0
    !Content-Type: text/plain;
    ! charset="iso-8859-1"
    !Content-Transfer-Encoding: 7bit
    !X-Newsreader: Microsoft CDO for Windows 2000
    !X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    !Thread-Index: AcNd5KqHAKRIhAGCQO+/UzVa2CgdIw==
    !Newsgroups: microsoft.public.dotnet.framework.aspnet.security
    !Path: cpmsftngxa06.phx.gbl
    !Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet.security: 6194
    !NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
    !X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.security
    !
    !Microsoft Knowledge Base Article - 306158
    ![[url]http://support.microsoft.com/default.aspx?scid=kb;en-[/url]
    !us;306158] shows a method to impersonate a specific user
    !in code via a web form.
    !
    !The trouble is that the impersonation isn't being
    !persisted accost the web application. Once the user moves
    !onto the next page they are back in the NT
    !AUTHORITY\SYSTEM security context.
    !
    !The desired scenario is:
    !1.) The user must enter there DOMAIN account username &
    !password into a WEB FORM (can't have the network logon
    !prompt popup).
    !
    !2.) The application must run in this users security
    !context as long as they are 'IN' the application. So every
    !page the user accesses within the application runs under
    !their security context.
    !
    !----------------------------------------------
    ! Subject: RE: Domain Authentication via Web Form -
    !PERSISTANCE?
    ! From: "Wei-Dong Xu [MSFT]" <v-wdxu@online.microsoft.com>
    !Sent: 8/7/2003 7:44:58 PM
    !
    !Hi Ty,
    !
    !In IIS6, if you choose the IIS6 worker process isolcation
    !mode(WPIM) to run
    !asp.net, the asp.net web application will run in a worker
    !process and the
    !application will decide how to impersonate the process. If
    !you select the
    !IIS5 isolation mode to execute the asp.net application,
    !the application
    !will run in aspnet process. The applicaiton will decide
    !his own entity as
    !well.
    !
    !It appears that this is a ASP.net develop issue, not IIS.
    !To better serve
    !you, the Asp.net support team has created a aspnet
    !newsgroup for you. I
    !think these asp.net experts will help you a lot on this
    !issue. Please go to:
    !Microsoft.public.dotnet.framework.aspnet
    !
    !Does this answer your question? Thank you for using
    !Microsoft NewsGroup!
    !
    !Wei-Dong Xu
    !Microsoft Product Support Services
    !Get Secure! - [url]www.microsoft.com/security[/url]
    !This posting is provided "AS IS" with no warranties, and
    !confers no rights."
    !----------------------------------------------
    !
    !


    Yan-Hong Huang[MSFT] Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139