Article ID: 970814 - View products that this article applies to.
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
If we have any session variables used in any custom Webparts or any custom pages in Sharepoint and these session variables are used to fetch data based on logged on user, then when we click on "sign in as different user" it does not clear out all the previous session values and cookies. This would not fetch us correct data in a custom Webpart.
When we use custom authentication with ISAPI filters sitting on MOSS, sign in as different user throws an error 401 Unauthorized.
Sign In as different user functionality available in the Welcome.ascx file does not clear out all the session and cookied values.
Make a copy of Init.js available under <Install drive>:Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033 and save it as Init_Original.js.
Search for method LoginAsAnother.
In the else part of the function comment out the below lines of code
var ch=url.indexOf("?") >=0 ? "&" : "?";
Add the below line of code:
Save the file.
Limitations of the above method: If a public update, a hotfix package, or a service pack is installed that contains updates to init.js file then the customization done to this file will be lost.
Modifying the files that are installed by SharePoint is not supported. When you modify these files, you must consider that they may be replaced by future updates and service packs. Additionally, there may be complications when you upgrade to later versions of the product. Keep backup copies of all customized files in case they are overwritten by an update. Product support will provide commercially reasonable support for help with modifications but will be unable to provide product changes or hotfixes that result from modifying the files that are installed by SharePoint.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Article ID: 970814 - Last Review: April 30, 2009 - Revision: 1.0