{"id":1583,"date":"2013-10-30T13:49:25","date_gmt":"2013-10-30T13:49:25","guid":{"rendered":"http:\/\/www.stuartroberts.net\/?p=1583"},"modified":"2013-11-28T14:43:21","modified_gmt":"2013-11-28T14:43:21","slug":"quick-tip-18","status":"publish","type":"post","link":"http:\/\/www.stuartroberts.net\/index.php\/2013\/10\/30\/quick-tip-18\/","title":{"rendered":"Loopback Check and 401.1 Error"},"content":{"rendered":"

SharePoint Short #18<\/strong><\/p>\n

If you’re developing a web service for SharePoint, or trying to access one of the SharePoint web services, through server code and get a 401.1 Unauthorized exception, it’s worth checking if the status of the loopback check, especially if you’re using a host name for the site.<\/p>\n

Since Windows 2003 (SP1) a loopback security check was added. The purpose of this check is to prevent access to the web application if there is an attempt to access it from the same server hosting the site, using a fully qualified domain name or host name.<\/p>\n

If you’re getting this exception on a dev\\test environment, the simplest solution is to disable the loopback check. Do this by opening the registry editor and navigate to the following key:<\/p>\n

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa<\/p>\n

From there, right click the LSA<\/em> folder and add a new DWORD value called DisableLoopbackCheck<\/em>. Set the value to 1<\/em> and then reboot the server. Do this for all Web Front Ends in the farm.<\/p>\n

If, on the other hand, this is happening on a production environment, do not<\/strong> disable the loopback check as this will remove a security check that may compromise your environment. Instead, add the host names that should bypass this check by adding another key to the registry:<\/p>\n

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa\\MSV1_0<\/p>\n

Right click the MSV1_0<\/em> folder and add a new Multi-String value called BackConnectionHostNames<\/em>. Set the value to the host name you want to exclude. If there are more than one, add them on separate lines and do not include the protocol, just the host name. Reboot the server and apply this to all Web Front Ends in the farm.<\/p>\n

For the last configuration, you could define a group policy to apply this across multiple servers, but I’ll leave that for another day!<\/p>\n","protected":false},"excerpt":{"rendered":"

SharePoint Short #18 If you’re developing a web service for SharePoint, or trying to access one of the SharePoint web services, through server code and get a 401.1 Unauthorized exception, it’s worth checking if the status of the loopback check, … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[33,44],"tags":[45],"class_list":["post-1583","post","type-post","status-publish","format-standard","hentry","category-configuration","category-shorts","tag-sharepoint-short"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t