RE: Access Denied on Cancelled Authentication (WSS 3.0)
- From: Carl <Carl@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 25 Mar 2008 08:46:04 -0700
"ids" wrote:
Have you received any responses to your post yet? We are also trying to.
accomplish the same thing as you, and have not been able to determine where
we need to perform these modifications. If you've received any information,
please let me know.
Thanks..
"fpmatt" wrote:
Hello everybody,
I'm looking to complete a largely successful SharePoint Services
installation (details at the end of the email), and I'm hoping that
somebody might be able to help with a few straggling issues.
I'm separating things into three posts in hopes it will increase
clarity. This is the last issue of the three.
QUESTION: How can I trap the Access Denied (401 error) a user receives
when cancelling through or otherwise failing Windows authentication
(NTLM)?
When I cancel the browser credential prompt WSS issues as a result of
Windows authentication, I get a rather plain Access Denied page.
Investigation of browser headers, indicates this is a 401 error.
(Logs seem to imply it's a 401.1 followed by a 401.5)
In trying to catch this (and redirect to something more friendly), I
can't override using IIS custom errors on the web application.
I also can't seem to override with custom errors in the web.config for
the application (though I would think the access denied would use the
SharePoint AccessDenied.aspx if the application were handling things).
Simply put, I know it's got to come from IIS through some means, but
can anybody point me to a way to isolate and change this behaviour.
Any pointers would be greatly appreciated.
Many thanks!
Matt
--[ Scenario Details ]--
Configuration Details:
- Windows Users batch generated and assigned to Windows Groups
- SharePoint Groups created to match Windows Groups
- Added Windows Groups as users to SharePoint Groups
In a nutshell, this allows an imperfect, but functional login
mechanism for Windows users to gain entry to SharePoint at appropriate
level. SharePoint creates users in UserInfo table on login, though
SharePoint can't see them until they are explicitly added later.
Technical Details:
- WSS 3.0
- Windows Server 2003 (pre-R2)
- IIS + SMTP
- SQL Server 2000 SP4
- Windows Authentication (NTLM)
- No Active Directory
- Prev by Date: Re: wss 3.0 host header named site collection
- Next by Date: RE: Access Denied on Cancelled Authentication (WSS 3.0)
- Previous by thread: column names (field names) from the custom list in sharepoint
- Next by thread: RE: Access Denied on Cancelled Authentication (WSS 3.0)
- Index(es):
Relevant Pages
|
