Microsoft KB Archive/263747

= OWS.MiscApis.1 Incorrectly Identifies the User as the Proxy Account =

Article ID: 263747

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft FrontPage 2000 Server Extensions, when used with:
 * the hardware: Intel x86

-



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=&quot;VBSCRIPT&quot; %> <% On Error Resume Next ContentVersion = 2512 If IsEmpty(Session(&quot;MiscApis&quot;)) Then Set Session(&quot;MiscApis&quot;) = Server.CreateObject(&quot;OWS.MiscApis.1&quot;) End if If Not IsEmpty(Session(&quot;MiscApis&quot;)) Then Session(&quot;MiscApis&quot;).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 &quot;proxy&quot; 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.

Keywords: kbprb KB263747

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.