Re: VPN & Windows authentication

On May 21, 8:58 am, SpaceMarine <spacemar...@xxxxxxxxxxxxxx> wrote:
i have never coded for this before. how can authentication work in
this setup? can my web app still use Windows authentication & pick up
those VPN users, or must it use a forms-based (AD) membership
provider?

ok, after messing around some more i have it. using VPN is no problem
at all, and my web apps can continue to use Windows authentication
from the web.config. the server OS simply asks the browser to popup
the login box (dunno what you call that box...NTML? SAMS? not sure).
after the user enters his credentials, the app sees him as his Windows
user.

cool!


thanks,
sm
.

Relevant Pages

  • IIS 7 Windows Authentication - Setting Default Domain For Remote U
    ... I have an asp.net web app that I need to have available internally and ... externally to our active directory users. ... I have windows authentication ... turned on so that the users crendentials will be passed to the sql server the ...
    (microsoft.public.inetserver.iis.security)
  • ASP.NET Authentication and Windows Authentication
    ... Windows Authentication, so users can access the application without the need ... of filling out a login page. ... According which user is using the web app, he/she'll have a dinamic menu, ... who is accessing the web app, and how to make it secure. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: strange authentication problem...
    ... What the problem is that i already have a login page which all works ... fine...however i have 3 pages in my web app, that whenever i go to their ... URL, they always popup the windows authentication window, when it shouldnt ... >> I have a login page, that when the user comes to it, it first pops up a ...
    (microsoft.public.dotnet.framework.aspnet)
  • revoke Windows authentication credentials for a session
    ... I am writing a web app that uses windows authentication. ... I have a logout ... button in the app that abandons session and returns the user to the main page ...
    (microsoft.public.dotnet.security)