OWS.MiscApis.1 Incorrectly Identifies the User as the Proxy Account (263747)
The information in this article applies to:
- FrontPage 2000 Server Extensions from Microsoft, when used with:
This article was previously published under Q263747 SYMPTOMS
The Office Server Extension component, OWS.MiscApis.1, uses the LOGON_USER server variable to identify the client that sends a comment to a discussion. An ISAPI filter is used to map thousands of users to several Windows NT accounts (proxy accounts). LOGON_USER, in this case, is the proxy account; therefore OWS.MiscApis.1 incorrectly identifies the user as the proxy account.
CAUSE
Office Server Extensions 2000 has functionality that allows users to have on line discussions. When the user watches this, they see who makes each comment. This is taken care of by a COM object in the following .asp file:
>>
<%@ Language="VBSCRIPT" %>
<%
On Error Resume Next
ContentVersion = 2512
If IsEmpty(Session("MiscApis")) Then
Set Session("MiscApis") = Server.CreateObject("OWS.MiscApis.1")
End if
If Not IsEmpty(Session("MiscApis")) Then
Session("MiscApis").HandleClientRequest
End If
%>
<<
The COM object accesses the ASP intrinsics and uses the LOGON_USER variable to identify the user. If an ISAPI filter is used to authenticate thousands of users and assigns those users to one of four "proxy" accounts, end users see the discussion taking place between the proxy accounts and incorrectly identify the proxy account as the LOGON_USER.
RESOLUTION
This problem will be resolved in OWS10.
| Modification Type: | Major | Last Reviewed: | 10/23/2003 |
|---|
| Keywords: | kbprb KB263747 |
|---|
|