Re: Intranet app via remote location (Internet)
- From: Troy S. <TroyS@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Apr 2008 07:09:02 -0700
... Just enable Windows
auth in IIS, disable anonymous and set ASP.NET to Windows auth mode. It
just works. If the IIS box is domain-joined, it will authenticate against
AD. There is no code to write.
Those are specific instructions that even I understand. I will give that a
go and see if it passes the client's muster.
The question is still whether you want to use Windows auth or forms auth.
If you choose to go with forms auth, the AD membership provider is the
easiest solution.
I wish I knew. From what little I understand, using Windows auth from
outside the Internet firewall is inviting headaches but that's just based on
random postings I've reviewed. I've looked at the AD m.p. and it doesn't
seem too complicated (still not a plug-n-play kind of option--I love
programming but hate the security-related quicksand). If the above option is
shot down then I'll tackle the AD MP option.
Thanks again for your time and effort.
Troy S.
.
- References:
- Intranet app via remote location (Internet)
- From: Troy S.
- Re: Intranet app via remote location (Internet)
- From: Joe Kaplan
- Re: Intranet app via remote location (Internet)
- From: Troy S.
- Re: Intranet app via remote location (Internet)
- From: Joe Kaplan
- Intranet app via remote location (Internet)
- Prev by Date: Re: Intranet app via remote location (Internet)
- Next by Date: System.Net.Cookie vs System.Web.Cookie
- Previous by thread: Re: Intranet app via remote location (Internet)
- Next by thread: PerformanceCounterCategory.Create() takes 3 minutes to add a new category!! How come? What can cause this?
- Index(es):
Relevant Pages
|