You may also be interested in: O'Reilly - SharePoint 2010 at Work
Editor's note: Contributor Gokan Ozcifci is a SharePoint Consultant at Vision IT Group. Follow him @gokanozcifci
In Microsoft SharePoint Server 2013, you will notice that the Sign in as Different User menu option is missing.
This was a great tool for developers and IT Pro's who wanted to test their solutions or customizations. In the new version of SharePoint I'm realy missing this option.
I'm not sure why they have removed it. There can be multiple reasons like
- Caching Problems
- Documents opened in external applications are saved with an unexpected user account
- Page content shows information from the previous user due to cached information
- Session variables contain information from previous users as the cookies are not cleared
Stefan Goßner explains that The Sign in as Different User functionality is not meant to be used as a security feature!
This feature allows users who have more than one AD account to quickly login with a different account to SharePoint - but it does not guarantee that no artifacts from the previous user remain!
If you have to guarantee that one user cannot see data from a different user you have to logoff/logon in Windows. Don't use the Sign in as a different user.
To work around this issue, use one of the following methods.
- Start Windows Internet Explorer by using the Run as different user option, and then go to the SharePoint site
- Access the SharePoint site by using the following URL:
Locate and then open the following file in a text editor:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES\Welcome.ascx ( use always a copy ).
Add the following element before the existing "ID_RequestAccess" element:
<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"
MenuGroupId="100" Sequence="100" UseShortId="true" />
Save the file.
Another way is to use a runas.exe shortcut to launch browser as another user. Less convenient, but more reliable in the long run.
It's really not a bad thing to remove this feature. We won't get users complaining anymore about cache and permission issues. But as an IT Pro I will miss it when we are going to troubleshoot on the user’s desk.