Basic Authentication domains don't work properly
From: 3ryon 5utherland (bryons_at_home.com)
Date: 03/30/04
- Next message: dee: "favorites"
- Previous message: Ohaya: "Re: Problem with IIS5 - "expired" CRLs not working?"
- Next in thread: Ken Schaefer: "Re: Basic Authentication domains don't work properly"
- Reply: Ken Schaefer: "Re: Basic Authentication domains don't work properly"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 29 Mar 2004 15:08:15 -0800
Here is my setup:
Web Server is in DomainAD, which I want all users to authenticate
against when logging into the web site. Most users are logged into a
machine using DomainNT, with a few users logged into DomainAD (we're
in the early stages of an AD migration).
I would like the web site to allow both Integrated Auth (for users who
are already in DomainAD), and Basic Auth (for users who are still
logged in to DomainNT). When I turn on Integrated and Basic (pointing
to DomainAD) the DomainAD people work great, but the DomainNT people
must type in DomainAD\Username for their login. Just typing in their
user name does not work, it seems to ignore the hard coded Domain
value. Most of these users won't be able to remember that.
If I turn off Integrated Auth and just allow Basic Auth it uses the
value specified in the Domain field, but this causes issues with the
Search feature in Sharepoint, which is probably not an acceptable
solution. Is there some reason that Basic Auth ignores the domain
value it's pointed to when Integrated Auth is also enabled? Is there
a way to get around it?
- Next message: dee: "favorites"
- Previous message: Ohaya: "Re: Problem with IIS5 - "expired" CRLs not working?"
- Next in thread: Ken Schaefer: "Re: Basic Authentication domains don't work properly"
- Reply: Ken Schaefer: "Re: Basic Authentication domains don't work properly"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
