Re: Complicated Fallback ASP.NET Security
From: Shawn Wheatley (swheatley22_at_yahoo.com)
Date: 01/16/04
- Next message: Joe Kaplan \(MVP - ADSI\): "Re: Complicated Fallback ASP.NET Security"
- Previous message: adam: "RE: caspol & local intranet security"
- In reply to: Shawn Wheatley: "Re: Complicated Fallback ASP.NET Security"
- Next in thread: Joe Kaplan \(MVP - ADSI\): "Re: Complicated Fallback ASP.NET Security"
- Reply: Joe Kaplan \(MVP - ADSI\): "Re: Complicated Fallback ASP.NET Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 16 Jan 2004 10:47:01 -0800
Ok, here's my latest update:
I found the following posting,
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=utf-8&selm=Rnw8J81PCHA.1712%40cpmsftngxa07
which loosely explains how to do a joint NTLM/Passport authenticated
site, with a database for roles. I have been able to modify this
slightly to work for my own form authentication (actually using
<authentication="None"> though) Basically I have to manage a cookie
or session object that lets the system know the user is logged in.
I'm trying to follow the example in 5A of that posting. It has an
NTLM authenticated page which errors out to a form for logging in if
the user can't authenticate. Thus, the entire site has no .NET
managed authentication, and all but this one NTLM authenticated page
are anonymous.
Example:
ntlm.aspx - NTLM authenticated, if not, redirect to
forms.aspx
forms.aspx - form, anonymous access
Page3.aspx - once authenticated go here
anyotherpage.aspx - redirect to ntlm.aspx if not authenticated.
The problem is that whenever the ntlm.aspx fails authenticating, it
can't successfully redirect to the forms.aspx as the IIS properties
specify.
Any ideas?
Shawn
> "Joe Kaplan \(MVP - ADSI\)" <joseph.e.kaplan@removethis.accenture.com> wrote in message news:<eHYKy##2DHA.632@TK2MSFTNGP12.phx.gbl>...
>
> > I'm pretty sure you would need to authenticate the ADAM users via LDAP and
> > some kind of Forms authentication as they aren't Windows users and can't be
> > authenticated via the normal SSPI stuff. You could also authenticate your
> > Windows users against ADAM using its proxy authentication stuff, but then
> > you won't have WindowsPrincipals for your web users.
> >
> > From there you could get clever and do something like calling LogonUser for
> > the Windows users to build a real Windows logon token if you needed that,
> > but there isn't any way to get a token for the ADAM users, so it might be
> > best to treat them uniformly.
> >
> > Hopefully that gave you some good ideas and didn't confuse you. I haven't
> > played with ADAM much yet, so this is all based on my current understanding
> > and reading a lot of newsgroup posts about it. But I am pretty sure this
> > info is accurate.
> >
> > Joe K.
- Next message: Joe Kaplan \(MVP - ADSI\): "Re: Complicated Fallback ASP.NET Security"
- Previous message: adam: "RE: caspol & local intranet security"
- In reply to: Shawn Wheatley: "Re: Complicated Fallback ASP.NET Security"
- Next in thread: Joe Kaplan \(MVP - ADSI\): "Re: Complicated Fallback ASP.NET Security"
- Reply: Joe Kaplan \(MVP - ADSI\): "Re: Complicated Fallback ASP.NET Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|