Steve Lineberry

Mixing Mobile Friendly Forms based auth with NTLM Windows auth in SharePoint

Steve Lineberry — Thu, 25 Feb 2016 17:16:54 +0000

One of the complaints I hear often is when users on mobile devices, mainly iOS, attempt to login to SharePoint. Typically they are presented with a popup box asking for their username and password but there isn’t an option to save the password. This is because our SharePoint web applications are using NTLM windows authentication because this is the most compatible with desktop PCs and provides the most functionality in SharePoint. Apple is decidedly “nerfing” their safari browser to force more apps to be sold which makes them more money. Part of this is them not providing an option to save passwords for NTLM authenticated sites and thus requiring apps to be made to support browsing SharePoint.

I’ve been working on this problem for a while. Because of BI and some other features we couldn’t move away from Windows authentication for SharePoint. So last year a coworker and I worked on creating our own browser app in iOS which would save user’s credentials and allow access to our SharePoint sites. The problem with this approach is now we are developing a commodity, a web browser, which could end up taking a lot of time and effort for not much benefit. After a long year last year working on many projects I got some breathing room at the beginning of this year and my brain decided to work on this problem and I came up with an idea.

Since I know SharePoint takes a windows principal and converts it into a windows claim, what if I could inject myself right BEFORE it converts the principal into a claim and replace the principal with a user of my choice. I reflectored the code in Microsoft.SharePoint.IdentityModel.SPWindowsClaimsAuthenticationHttpModule and found the right spot and after building my own httpmodule and configuring it to run before SharePoint’s (see web.config example below), I was able to change the currently logged in user to be one of my choice. This was great because this meant that I could potentially create a forms based experience for mobile devices and then tell SharePoint to use that user instead of thinking we weren’t authenticated. The reason forms based authentication is needed is because iOS supports remembering passwords for forms based authentication.

SharePoint web.config


...
 
 ...
 
 
 ...
 
...

Notice in the httpmodule below that I am checking to see if the useragent of the device is a mobile device on line 21. Then I am checking if the status being returned is a 401 (unauthorized) on line 39. Originally those were the only rules I had in place before I redirected to my forms login page. But then I ran into some issues with the SharePlus app, which uses the same useragent as safari, trying to use webservices and requesting files and it didn’t understand our new authentication. So i placed some other checks in there to determine whether it was a request from a browser or from an app. Apps never have referrers set, so I check that first (line 59), and then I have a few other checks in place including looking at the querystring for web=1 (line 69) which is what SP uses to open files in the office web apps (office online). So if i think this request is coming from a mobile device and it’s not an app, then I redirect to my special login page (line 85), otherwise I add some headers (line 90) which may not be needed but potentially apps such as office might be interested in.

HttpModule – PreSendRequestHeaders

public class WindowsFormLogin : IHttpModule
{
	public void Init(HttpApplication context)
	{
		if (context == null)
		{
			return;
		}
		context.AuthenticateRequest += context_AuthenticateRequest;
		context.PreSendRequestHeaders += context_PreSendRequestHeaders;
	}

	void context_PreSendRequestHeaders(object sender, EventArgs e)
	{
		HttpApplication httpApplication = sender as HttpApplication;
		HttpContext context = httpApplication.Context;

		if (context == null) return;
		if (context.Request == null) return;
		if (context.Request.Browser == null) return;
		if (false == context.Request.Browser.IsMobileDevice) return;
		

		if (context.Request.Cookies[Constants.MOBILE_LOGIN_EXCLUDE_COOKIE_NAME] != null)
		{
			string cookieValue = context.Request.Cookies[Constants.MOBILE_LOGIN_EXCLUDE_COOKIE_NAME].Value;
			bool exclude;
			if (false == bool.TryParse(cookieValue, out exclude))
			{
				exclude = false;
			}

			if (exclude) return;
		}

		string userAgent = context.Request.ServerVariables["HTTP_USER_AGENT"];
		if (userAgent.Contains("AppleWebKit") &&
		    false == userAgent.Contains("Safari")) return;

		int status = context.Response.StatusCode;
		switch (status)
		{
			case 401:
				if (IsPageRequest(context))
		                    {
		                        HandlePageRequest(context);
		                    }
		                    else
		                    {
		                        HandleNonPageRequest(context);
		                    }
				
				break;
		}
	}

private bool IsPageRequest(HttpContext context)
        {
            if (context.Request.Url == null) return false;
            if (string.IsNullOrEmpty(context.Request.Url.AbsolutePath)) return false;

            if (context.Request.UrlReferrer != null &&
                false == string.IsNullOrEmpty(context.Request.UrlReferrer.ToString()))
            {
                return true;
            }

            if (context.Request.Url.AbsolutePath.ToLower().EndsWith(".aspx")) return true;
            if (context.Request.Url.AbsolutePath.Contains("/_layouts/")) return true;
            if (context.Request.Url.AbsolutePath.Contains("/_")) return false;

            if (context.Request.QueryString["web"] != null &&
                context.Request.QueryString["web"] == "1")
            {
                return true;
            }

            try
            {
                if (SPContext.Current.Web.ServerRelativeUrl.ToLower() == context.Request.Url.AbsolutePath.ToLower()) return true;
            }
            catch { }

            return false;
        }

        private void HandlePageRequest(HttpContext context)
        {
            context.Response.Redirect("/_mobilelogin/Home/Login?ReturnUrl=" + HttpUtility.UrlEncode(context.Request.Url.ToString()));
        }

        private void HandleNonPageRequest(HttpContext context)
        {
            if (context.Response.Headers["X-Forms_Based_Auth_Required"] == null)
            {
                context.Response.Headers.Add("X-Forms_Based_Auth_Required", "/_mobilelogin/Home/Login?ReturnUrl=" + HttpUtility.UrlEncode(context.Request.Url.ToString()));
            }
            if (context.Response.Headers["X-Forms_Based_Auth_Return_Url"] == null)
            {
                Uri relativeUri;
                Uri.TryCreate("/" + SPUtility.ContextLayoutsFolder + "/error.aspx", UriKind.Relative, out relativeUri);
                string absoluteUri2 = new Uri(SPAlternateUrl.ContextUri, relativeUri).AbsoluteUri;
                context.Response.Headers.Add("X-Forms_Based_Auth_Return_Url", absoluteUri2);
            }

            if (context.Response.Headers["X-MSDAVEXT_Error"] == null)
            {
                string value = "917656; " + HttpUtility.HtmlAttributeEncode(SPResource.GetString("FormsAuthenticationNotBrowser", new object[0]));
                context.Response.Headers.Add("X-MSDAVEXT_Error", value);
            }
        }


}

I decided to create a ASP.NET MVC web application for my login page. For things to work as expected, this needs to be hosted in your SharePoint farm. I decided to add it as a virtual directory called _mobilelogin in IIS under my SharePoint web applications. Because I need a windows principal object later, I need to store the person’s username and password somewhere I can get to it later. There are a few different ways of handling this, each with their own pros and cons but to keep things simple for this blog post, I will use the FormsAuthenticationTicket (line 70) that normal ASP.NET Forms based authentication uses to store both the userid and password. This ticket gets encrypted (line 78) and stored as a cookie in the browser of the mobile device (line 84). Since the password is sensitive, it will be doubly encrypted because it gets encrypted once (line 75) and then put into the ticket which gets encrypted again.

MVC Model and Controller

public class LoginModel
{
	public string UserName { get; set; }
	public string Password { get; set; }
	public bool CookieSet { get; set; }
	public bool RememberMe { get; set; }
}
	
public class HomeController : Controller
{
	[HttpGet]
	[OutputCache(NoStore = true, Duration = 0, VaryByParam = "None")] 
	public ActionResult Login()
	{
		LoginModel mdl = new LoginModel();
		mdl.RememberMe = true;
		try
		{
			if (Request.Cookies[Constants.MOBILE_LOGIN_COOKIE_NAME] != null)
			{

				string cookieValue = Request.Cookies[Constants.MOBILE_LOGIN_COOKIE_NAME].Value;

				if (false == string.IsNullOrEmpty(cookieValue))
				{
					FormsAuthenticationTicket ticket = FormsAuthentication.Decrypt(cookieValue);
					if (ticket.Expired)
					{
						Utility.LogoutHelper(Response);
					}
					else
					{
						mdl.UserName = ticket.Name;
						mdl.CookieSet = true;
					}
				}
			}
		}
		catch (Exception e)
		{
			ViewBag.ErrorMsg = e.Message;
		}

		return View(mdl);
	}

	[HttpPost]
	[OutputCache(NoStore = true, Duration = 0, VaryByParam = "None")] 
	public ActionResult Login(LoginModel mdl)
	{
		try
		{
			if (false == string.IsNullOrEmpty(mdl.UserName) &&
				false == string.IsNullOrEmpty(mdl.Password))
			{
				string username = mdl.UserName;
				if (false == Utility.IsAnEmailAddress(username) &&
					string.IsNullOrEmpty(Utility.ExtractDomain(username)))
				{
					username = ConfigurationManager.AppSettings["DefaultDomain"] + "\\" + username;
				}
				WindowsIdentity identity = Utility.Logon(username, mdl.Password);

				DateTime expiration = DateTime.Now.AddMinutes(Constants.MOBILE_LOGIN_TTL_SHORT_MIN);
				if (mdl.RememberMe)
				{
					expiration = DateTime.Now.AddDays(Constants.MOBILE_LOGIN_TTL_LONG_DAYS);
				}

				FormsAuthenticationTicket ticket = new FormsAuthenticationTicket(1,
					username,
					DateTime.Now,
					expiration,
					mdl.RememberMe,
					Utility.Protect(mdl.Password, Constants.MOBILE_LOGIN_SALT),
					FormsAuthentication.FormsCookiePath);

				HttpCookie cookie = new HttpCookie(Constants.MOBILE_LOGIN_COOKIE_NAME, FormsAuthentication.Encrypt(ticket));
				if (mdl.RememberMe)
				{
					cookie.Expires = ticket.Expiration;
				}
				Utility.SetAttributes(cookie);
				Response.Cookies.Add(cookie);

				HttpCookie cookieExclude = new HttpCookie(Constants.MOBILE_LOGIN_EXCLUDE_COOKIE_NAME, false.ToString());
				Utility.SetAttributes(cookieExclude);
				cookieExclude.Expires = DateTime.Now.AddDays(-1);
				Response.Cookies.Add(cookieExclude);
				
				Redirect();
			}
			else
			{
				ViewBag.ErrorMsg = "Please fill in both the UserName and Password fields.";
			}
		}
		catch (Exception e)
		{
			ViewBag.ErrorMsg = e.Message;
		}

		return View(mdl);
	}

	public ActionResult Logout()
	{
		Utility.LogoutHelper(Response);

		return View();
	}

	[OutputCache(NoStore = true, Duration = 0, VaryByParam = "None")] 
	public ActionResult Exclude()
	{
		HttpCookie cookieExclude = new HttpCookie(Constants.MOBILE_LOGIN_EXCLUDE_COOKIE_NAME, true.ToString());
		Utility.SetAttributes(cookieExclude);
		Response.Cookies.Add(cookieExclude);

		Utility.LogoutHelper(Response);
		Redirect();

		return View();
	}

	private void Redirect()
	{
		string returnUrl = "/";
		if (false == string.IsNullOrEmpty(Request.QueryString["ReturnUrl"]))
		{
			returnUrl = HttpUtility.UrlDecode(Request.QueryString["ReturnUrl"]);
		}

		Response.Redirect(returnUrl);
	}
}

MVC View

@model LoginModel

@{
    ViewBag.Title = "Login";
}



    
        
            @using (Html.BeginForm())
            {
                
                    
                        
                            This is a special login page just for mobile devices.  If you feel you reached this page in error, @Html.ActionLink("click here to restore normal login functionality", "Exclude", "Home").
                        
                    
                    
                        
                            @if (false == string.IsNullOrEmpty(ViewBag.ErrorMsg))
                            {
                                @ViewBag.ErrorMsg
                            }
                        
                    
                    @if (Model.CookieSet)
                    {
                        
                            
                                
                                    You are currently logged in as: @Model.UserName 

                                    @Html.ActionLink("Click here to logout", "Logout", "Home", new { ReturnUrl = Request.QueryString["ReturnUrl"] }, new { } ).
                                
                            
                        
                        
                            
                                
                                    @if (string.IsNullOrEmpty(Request.QueryString["ReturnUrl"]))
                                    {
                                        Return to site
                                    }else{
                                        Return to site
                                    }
                                
                            
                        
                    }
                    else
                    {
                    
                        @Html.Label("User Name", new { @class = "col-sm-3 control-label" })
                        
                            @Html.TextBoxFor(m => m.UserName, new { @class = "form-control" })
                            @Html.ValidationMessageFor(m => m.UserName, null, new { @class = "help-inline" })
                        
                    
                    
                        @Html.LabelFor(m => m.Password, new { @class = "col-sm-3 control-label" })
                        
                            @Html.PasswordFor(m => m.Password, new { @class = "form-control" })
                            @Html.ValidationMessageFor(m => m.Password, null, new { @class = "help-inline" })
                        
                    
                    
                        
                            
                            @Html.Label("Remember Me")
                            @Html.CheckBoxFor(m => m.RememberMe, new { @checked = "checked" })
                        
                    
                    
                        
                            If you have previously saved your password in your browser, select the username field above and then select autofill password at the top of the onscreen keyboard.
                        
                    
                    }
                    

                
            }

After we set the cookie in our MVC application, we need to redirect back to where we came from. Then the HttpModule from earlier kicks in but on a different event: AuthenticateRequest. Notice on line 26 where our Ticket gets unencrypted and I check to make sure it is still valid and not expired. After that I get a WindowsIdentity object by logging in as the user with their username and password (line 33). I then create a WindowsPrincipal object from the identity and assign it to the user property of the HttpContext (line 36). This HttpContext.User property is what the SPWindowsClaimsAuthentication HttpModule will look at when creating the Windows Claim which SharePoint then uses everywhere. I also hijack the signout page on line 38 to redirect to our forms logout page when we are logged in using our forms method.

HttpModule – AuthenticateRequest

public class WindowsFormLogin : IHttpModule
{
	public void Init(HttpApplication context)
	{
		if (context == null)
		{
			return;
		}
		context.AuthenticateRequest += context_AuthenticateRequest;
		context.PreSendRequestHeaders += context_PreSendRequestHeaders;
	}

	void context_AuthenticateRequest(object sender, EventArgs e)
	{
		HttpApplication httpApplication = sender as HttpApplication;
		HttpContext context = httpApplication.Context;

		try
		{
			if (context.Request.Cookies[Constants.MOBILE_LOGIN_COOKIE_NAME] == null) return;

			string cookieValue = context.Request.Cookies[Constants.MOBILE_LOGIN_COOKIE_NAME].Value;

			if (false == string.IsNullOrEmpty(cookieValue))
			{
				FormsAuthenticationTicket ticket = FormsAuthentication.Decrypt(cookieValue);
				if (ticket.Expired)
				{
					throw new ApplicationException("Mobile Login Expired");
				}

				string user = ticket.Name;
				WindowsIdentity identity = Utility.Logon(user, Utility.Unprotect(ticket.UserData, Constants.MOBILE_LOGIN_SALT));

				context.Request.ServerVariables["LOGON_USER"] = user;
				context.User = new WindowsPrincipal(identity);

				int index = context.Request.RawUrl.ToLower().IndexOf("/_layouts/15/signout.aspx");
				if (index >= 0)
				{
					string returnUrl = "/";
					if (index > 0)
					{
						returnUrl = context.Request.RawUrl.ToLower().Substring(0, index);
					}
					if (context.Request.UrlReferrer != null &&
						false == string.IsNullOrEmpty(context.Request.UrlReferrer.ToString()))
					{
						returnUrl = context.Request.UrlReferrer.ToString();
					}
					context.Response.Redirect("/_mobilelogin/Home/Logout?ReturnUrl=" + HttpUtility.UrlEncode(returnUrl));
				}
			}
		}
		catch (Exception ex)
		{
			//MobileLogin Login Error
			Utility.LogoutHelper(context);
		}
	}
}

I have used a few helper methods in my code above so below is this code which should enable you to put this solution together in your own environment. Also, the MVC login app pool service account and your SharePoint app pool service account need special permissions on the server in order for them to login as another user on line 61. This permission is called “Act as part of the operating system” which can be found in user rights assignment in local security policies.

Utility Class

public class Constants{
	public const string MOBILE_LOGIN_COOKIE_NAME = "MobileLogin";
	public const string MOBILE_LOGIN_EXCLUDE_COOKIE_NAME = "MobileLoginExcluded";
	public const int MOBILE_LOGIN_TTL_LONG_DAYS = 90;
	public const int MOBILE_LOGIN_TTL_SHORT_MIN = 90;
	public const string MOBILE_LOGIN_SALT = "TEST 123";
}

public class Utility
{
	public static string Protect(string text, params string[] purpose)
	{
		if (string.IsNullOrEmpty(text))
			return null;

		byte[] stream = Encoding.UTF8.GetBytes(text);
		byte[] encodedValue = MachineKey.Protect(stream, purpose);
		return HttpServerUtility.UrlTokenEncode(encodedValue);
	}
	public static string Unprotect(string text, params string[] purpose)
	{
		if (string.IsNullOrEmpty(text))
			return null;

		byte[] stream = HttpServerUtility.UrlTokenDecode(text);
		byte[] decodedValue = MachineKey.Unprotect(stream, purpose);
		return Encoding.UTF8.GetString(decodedValue);
	}

	public static WindowsIdentity Logon(string username, string password)
	{
		string domain = Utility.ExtractDomain(username);
		username = Utility.ExtractName(username);

		IntPtr handle = new IntPtr(0);
		handle = IntPtr.Zero;

		const int LOGON32_LOGON_NETWORK = 3;
		const int LOGON32_PROVIDER_DEFAULT = 0;

		// attempt to authenticate domain user account
		bool logonSucceeded = LogonUser(username, domain, password, LOGON32_LOGON_NETWORK, LOGON32_PROVIDER_DEFAULT, ref handle);

		if (!logonSucceeded)
		{
			// if the logon failed, get the error code and throw an exception
			int errorCode = Marshal.GetLastWin32Error();
			throw new Exception("User logon failed. Error Number: " + errorCode);
		}

		// if logon succeeds, create a WindowsIdentity instance
		WindowsIdentity winIdentity = new WindowsIdentity(handle, "NTLM");

		// close the open handle to the authenticated account
		CloseHandle(handle);

		return winIdentity;
	}

	[DllImport("advapi32.dll", SetLastError = true)]
	private static extern bool LogonUser(string lpszUsername,
										string lpszDomain,
										string lpszPassword,
										int dwLogonType,
										int dwLogonProvider,
										ref IntPtr phToken);

	[DllImport("kernel32.dll", CharSet = CharSet.Auto)]
	private static extern bool CloseHandle(IntPtr handle);
	
	public static bool IsAnEmailAddress(string text)
	{
		if (text == null) return false;
		if (text.Length <= 0) return false;
		if (text.IndexOf(" ") >= 0) return false;

		string patternLenient = @"\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*";
		Regex reLenient = new Regex(patternLenient);
		string patternStrict = @"^(([^<>()[\]\\.,;:\s@\""]+"
			+ @"(\.[^<>()[\]\\.,;:\s@\""]+)*)|(\"".+\""))@"
			+ @"((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}"
			+ @"\.[0-9]{1,3}\])|(([a-zA-Z\-0-9]+\.)+"
			+ @"[a-zA-Z]{2,}))$";
		Regex reStrict = new Regex(patternStrict);
		return reStrict.IsMatch(text);
	}

	public static string ExtractDomain(string UserName)
	{
		if (UserName.IndexOf(Convert.ToChar("\\")) > 0)
		{
			string[] fullDomainUserName = UserName.Split(new char[] { '\\' }, 2);
			return fullDomainUserName[0];
		}
		else
		{
			return string.Empty;
		}
	}

	public static string ExtractName(string name)
	{
		if (name.IndexOf(Convert.ToChar("\\")) > 0)
		{
			string[] fullDomainName = name.Split(new char[] { '\\' }, 2);
			return fullDomainName[fullDomainName.Length - 1];
		}
		else
		{
			return name;
		}
	}
	
	public static void SetAttributes(HttpCookie cookie, HttpContext context)
	{
		cookie.HttpOnly = true;
		string domain = GetRootCookieDomain(GetBasePath(context));
		if (false == string.IsNullOrEmpty(domain) &&
			domain.Contains('.'))
		{
			cookie.Domain = domain;
		}
	}

	public static void LogoutHelper(HttpContext context)
	{
		try
		{
			HttpCookie cookie = new HttpCookie(Constants.MOBILE_LOGIN_COOKIE_NAME, string.Empty);
			cookie.Expires = DateTime.Now.AddDays(-1);
			SetAttributes(cookie, context);

			context.Response.Cookies.Add(cookie);
		}
		catch (Exception err)
		{
			//MobileLogin Logout Cookie Error
		}
	}
	
	public static string GetRootCookieDomain(string url)
	{
		url = GetBasePathFromUrl(url);
		if (string.IsNullOrEmpty(url)) return url;
		Uri uri = new Uri(url);
		string host = uri.Host;
		if (false == host.Contains('.')) return uri.Host;

		string[] hostParts = host.Split('.');
		string domain = "." + hostParts[hostParts.Length - 2] + "." + hostParts[hostParts.Length - 1];

		return domain;
	}
	
	public static string GetBasePathFromUrl(string url)
	{
		string newUrl = string.Empty;
		if (url.Contains("://"))
		{
			newUrl = url.Substring(0, url.IndexOf("://") + 3);
			url = url.Substring(url.IndexOf("://") + 3, url.Length - url.IndexOf("://") - 3);
			if (url.Contains("/"))
			{
				newUrl += url.Substring(0, url.IndexOf("/"));
			}
			else
			{
				newUrl += url;
			}
		}
		return newUrl;
	}
	
	public static string GetBasePath(HttpContext context)
	{
		string basepath = "";
		if (context.Request.ServerVariables["HTTPS"].ToString().ToUpper().Equals("ON"))
		{
			basepath = "https://";
		}
		else
		{
			basepath = "http://";
		}
		basepath += context.Request.ServerVariables["SERVER_NAME"].ToString();
		if (!context.Request.ServerVariables["SERVER_PORT"].ToString().Equals("80") &&
			!context.Request.ServerVariables["SERVER_PORT"].ToString().Equals("443"))
		{
			basepath += ":" + context.Request.ServerVariables["SERVER_PORT"].ToString();
		}
		return basepath;
	}
}

Edit 05/18/2016:

Added a useragent check before the 401 status check to help with apps like the SharePoint iOS app and SharePlus which already know how to connect to SharePoint using NTLM.

SharePoint Cross Site Word Document Properties

Steve Lineberry — Thu, 04 Feb 2016 19:06:23 +0000

Recently I had a project where I was using SharePoint columns as document property fields in MS Word. This is pretty straight forward when you have one library and some files but when you have a central repository of master files that are then pushed out to different sites across your farm it makes it a little more interesting. We built our content types and columns in Visual Studio which were deployed on all sites and thus had the same contenttypeid’s and column guids. One thing I noticed was that in the master library the document field would work correctly but once the file was copied to another site the document field would no longer work. I was unable to find anything on the web about this scenario which is why I’m posting my findings here.

First thing I did was to open the copied file in one of the non-master sites and fix the field. I just deleted the old one and re-added it and everything was fine. Next I renamed both the fixed document and the master document to have a .zip extension. This enables me to extract the contents of the word file so I could examine the differences. What I found was that in the word\document.xml file where the document fields were inserted they had different GUIDs for the ns3 namespace attribute (see on line 21). Also check out the xpath statement on line 23 and then notice how the namespace (ns3) for our document field (ProjectName) is the namespace where we have different GUIDs between the two documents.


	
		
			
			
			
			
		
		
		
		
		
		
			
		
		
		
		
	
	
	
		
			
				
			
			[Project Name]

So following a hunch I looked up the SPWeb.ID and sure enough, it was the same GUID as ns3. So, when copying documents from one site to another, the document field xml data from SharePoint must be tied to the GUID of the site it came from. I was able to verify this by looking at the customXml\item1.xml file (it’s always makes things a lot easier to be able to view your xml data when working with xpath queries) which showed all of my document fields coming from SharePoint and they all had a namespace of the SPWeb.ID GUID.

Since the namespace will be changing every time I copy the file I decided to update the xpath query to ignore the namespace. Changing it from:

w:xpath="/ns0:properties[1]/documentManagement[1]/ns3:ProjectName[1]"

to:

w:xpath="/ns0:properties[1]/documentManagement[1]/*[local-name() = 'ProjectName'][1]"

This xpath trick will query only based on the name of the element and exclude any namespaces. Sure enough, once I updated the file in my master site and did another copy down to a non-master site, the field updated correctly in word and everything was happy. You can update the document.xml file using any text editor you’d like, and then just zip all of your files back up, and then rename the file to be a .docx and it should open correctly in word.

Microsoft Band 2 vs Fitbit Surge

Steve Lineberry — Fri, 22 Jan 2016 20:05:34 +0000

Microsoft Band 2

Last year I was debating between the Microsoft Band or the upcoming Fitbit Surge. After trying on the band at the Microsoft Store, I was not happy with how it felt on my wrist so I decided to go with the Surge. I’ve been using a Fitbit Surge everyday for most of the past year. For a fitness tracker with GPS, the Surge has been fantastic but I wanted some smartwatch features as well.

Fitbit Surge

After trying on the new Microsoft Band 2 at the Microsoft Store, I decided to get that one to replace my Surge. Here are my current thoughts on the Band 2 compared to the Surge.

Phone Compatibility

The Band 2 works with Android, iOS and Windows Phone but the Cortana (voice) integration isn’t available on Android and iOS,only on the Windows Phone and the onscreen keyboard isn’t available on iOS.

View Time and steps (secondary display item is configurable)

I have been using it with my Lumia 950 Windows Phone (see post here). The Fitbit Surge also works on Android, iOS and Windows Phone but some things didn’t work on the Windows Phone like phone/text notifications and music controls. I used my Surge mainly on a Windows Phone but my wife has been using it on her iPhone recently.

Same features as Fitbit Surge

Heart rate monitor

Displays the time and date
Tracks steps, calories burned, distance, floors, heartrate
GPS tracks runs
Tracks other workouts with heartrate like the elliptical
Alarms, timer, stopwatch

Pros over Fitbit Surge

More notifications
See full text messages, email partials, and my upcoming calendar
- Phone (Improvement for Windows Phone only)
- Text (Improvement for Windows Phone only)
- Email
- Facebook
- Facebook Messenger
- Calendar Reminders
Control music (Improvement for Windows Phone only)
Reply to texts and phone calls
- Up to 4 quick responses (with automatic detection of a question and showing yes and no as additional quick responses)
  The small keyboard used to reply to texts works surprisingly well
- Small keyboard to reply to text messages, which works surprisingly well (Windows Phone and Android only)
- Cortana voice dictation to reply to text messages (Windows phone only)
See weather, news, and calendar
Use Cortana to initiate reminders, texts, calls, etc. (Windows phone only)
- I can even ask questions like “How old is j-lo” and the answer shows up on the band screen.
  Cortana – “How old is J Lo?”
See last exercise and sleep
- On the fitbit this was only available to view using the app or the website, not on the watch itself
Sleep cycle alarm to wake you up, up to 30 mins before scheduled alarm
Prettier design and user interface
A lot better sleep stats compared to Fitbit
- Lots of people have mentioned that the Band 2 is a MUCH prettier watch than the fitbit surge.
- The fitbit surge is large and looks big on my wife where the band 2 would look fine on a male or a female
- The fitbit surge had a basic black and white interface whereas the band 2 is colorful and dynamic.
Less bulky
- Fitbit would get caught when tucking in my shirt, taking off my jacket, or putting on my backpack
Auto detected sleep mode or manual
- Manual is nice because it also turns off watch mode and notifications other than the watch alarms.
- Tracks how long it takes to go sleep.
Watch mode
- Off
- Always on
- Rotate
Lots more settings right on the watch, the fitbit had very few settings on the watch itself and was mostly configured using the app or website.
- Vibrate
- Dim
  Turning my wrist over turns on the low power watch mode for a few seconds
Tile and color settings using phone
- I can even create my own background pictures or download some to the device using additional apps
More info can be seen while during an activity
- The fitbit displayed a few pieces of data but that data wasn’t customizable. Any additional data I had to swipe through at the bottom of the screen.
- The band 2 allows me to configure what data I see on the main screen while during an activity and then it provides a single swipe right to see the rest of the data which I configured to be shown.
More analytics on the website and app
More exercise stats compared to Fitbit
- Vo2 max
- Max and mins (heart rate, elevation, etc)
- Recovery time
UV sensor tells me how long I was exposed to sunlight
- Considering it’s currently winter, I haven’t had a chance to use this a lot yet.

Cons/current issues

Health app
- ~~No weight tracking~~ – Now available in February Update
- No food tracking
  - The fitibit app is fantastic at tracking food
  - I used this functionality for a little bit with my fitbit to get an idea but it wasn’t something I did all the time.
- Not Universal Windows Platform and supporting continuum like the Fitbit app (WTH MS, can’t even utilize your own tech?)
Weird how different types of activities are grouped together
Best feel is wearing on bottom of wrist which feels kind of weird at first but I’ve gotten used to it.
The clasp took a little bit to get used to but it seems pretty solid
Battery life
- Fitbit is 5 days
  - I would put it on the charger while taking a shower, giving the kids a bath, and while at the climbing gym
    View from the top of my wrist shows the clasp with integrated battery and the UV sensor.
  - On climbing trips typically I would charge while driving to the location and that was usually enough to last the whole trip
- Band 2 is 24-48 hours
  - I’ve been charging mine nightly when I am sitting down to watch TV (it’s usually around 50% when I start charging)
  - Unsure how this is going to work when i am on climbing trips. I might have to forgo sleep tracking just to maintain a charge.

Conclusion

I’ve really enjoyed the Band 2. It’s been really handy when playing with my kids. I can put my phone down near by and glace at my watch when receiving texts from my wife or seeing emails come through. It beats trying to dig my phone out of my pocket only to see the text was from Chick-fil-a telling me about some deal they are running. I’ve also really enjoyed being able to text my wife or reply to texts from my wrist while playing with the kids or during other activities where my phone isn’t easily accessible. I wish the app was better and the battery life was a lot better but compared to the advantages, I can get over those things pretty quickly.

What I like and dislike about Windows 10 Phone

Steve Lineberry — Sun, 17 Jan 2016 03:53:57 +0000

Lumia 950 – 5.2″ Quad HD (AMOLED, 2560 x 1440), 6-core 1.8 Ghz proc, 3 GB of RAM, 32 GB storage with up to 200 GB expandable with microSD, Dual SIM, 20 MP Camera

So if you are new to Windows Phone, you can refer to my post here on why I like Windows Phone better than iOS. I recently have been playing around with Windows 10 Mobile on a Lumia 640 and a Lumia 950. This post is mainly my running list of what has improved in Windows 10 Mobile over Windows Phone 8.1 and listing what current cons and issues I have.

Pros over Windows Phone 8.1

Hey Cortana with learn my voice or use any voice
- Hey Cortana was only on select Windows Phone 8.1 devices
- Learn my voice is new in Windows 10 Phone
Continuum (See video demonstration here)
- Connect to a TV or monitor as a second larger screen to do work on
  Windows Hello – Iris Recognition
- Use phone as mouse and keyboard or connect usb/bluetooth devices
Mouse support
Windows Hello (Only on some devices)
- Iris recognition instead of typing a pin number
Outlook for email
- Attach any files on device to emails
- Attach from onedrive
Better organized settings
Keyboard joystick
- Dot near z and x to easily move the cursor around
Notification text and facebook inline reply
Voice dictation built into keyboard
Don’t forget when powering off
- Displays a reminder of your next appointment when you power off the device
  Notification inline reply, keyboard joystick, voice dictation easily accessible on keyboard
Call Recording
Fast USB-C charging (only on some devices)
- 50% in 30 mins

Cons/Current issues

NTLM passwords aren’t saved in Edge
Can’t connect to NTLM auth OneNote
Excel, PowerPoint and Word can’t connect to on-prem NTLM SharePoint
Airwatch blocks SD card – Confirmed bug with airwatch
Airwatch doesn’t install cert chain – Maybe fixed with a newer build
~~Cannot open EML attachment in email~~ – Fixed in Outlook Mail 17.6868.41032.0
Continuum
- Only run one app at a time, Can’t snap apps side by side
- Can’t run on two monitors, only phone screen and one monitor
- The apps below are not Universal Windows Platform (uwp) apps that support continuum
  Call screen including the record option
  - ~~remote desktop~~ (http://wmpoweruser.com/remote-desktop-preview-app-now-available-for-windows-10-mobile-with-continuum-support/)
  - Skype for business
  - Facebook messenger
  - Citrix Receiver
Option to only try Windows Hello when unlock is needed
- Right now Hello will get locked out from too many attempts because of notifications (email, text, etc)
Facebook app needs additional features and bug fixes
- Live tile not working – Better in 10.2.1.0
- Pinned pages don’t show notifications on live tile
- Some types of content don’t display correctly
  Windows Hello tries too much and ends up locking itself out
  - Memories
  - Birthday rollups
Battery life
- Better after installing 10586.63
Dual Sim
- ~~No Visual voicemail on dual sim devices~~ – Fixed in 14267.1004
- Should be a way to hide 2nd sim when not used in dual sim
- ~~No vibrate on answer on dual sim devices~~ – Fixed in 14283
OneDrive doesn’t connect to on-prem SharePoint
Live lock screen app from 8.1 isn’t available
Edge does not change to desktop user agent when used on continuum
- Whatever screen the tab is opened in is the user agent that will be used
~~Random reboots (a lot less after 10586.63)~~
- ~~Seemed to happen a lot more at my office. The following things are potentially different at my office vs at home.~~
  - ~~Bluetooth devices~~
  - ~~AT&T Microcell – Often after it reboots it says that my carrier has changed my SIM settings and I need to restart again.~~
  - ~~Wireless charging~~
- ~~Kids corner~~ (Fixed since 10586.71)
  - Since 10586.63, I’ve tried going to kids corner several times from the lock screen and the phone will freeze and eventually reboot. I have since figured out if I don’t try to hold it up to my face and let windows hello to attempt to sign me in, then I can go into kids corner successfully. It seems to be the combination of windows hello attempting to read my iris’s while I’m going to kids corner which locks it up.

Why I like Windows Phone better than iOS

Steve Lineberry — Sun, 17 Jan 2016 03:08:22 +0000

Customizable live tiles showing unread counts and information

The goal in the post is for me to document my running list of why I like Windows Phone better than iOS (iPhone/iPad).

Customizable home screen with three different tile sizes. This enables users that have a hard time seeing small text or hitting small buttons can make them bigger.
Live tiles show more information when not using the small size which shows alerts directly on the home screen whereas iOS only shows the number of notifications.
Swipe right enables viewing all installed apps with search and jump by alpha. Unlike iOS where every app installed has to be in a home page somewhere
Can have a combined tile for all email, separate tile for each email address or link several mailboxes together such as Gmail and Hotmail can be linked together as a personal inbox and keep work inbox separate
Swiping right shows all apps with easy to find by alpha or using search
Can combine tiles into a tile folder
Driving mode
- Reads texts to you over bluetooth
- Can dictate responses over bluetooth
- Does not popup or sound notifications for anything except phone and text
  - Can also turn off phone and/or text as well
Kids corner
- Swipe right to show a start screen that you configured just for your kids and the apps they are allowed to use
- Need PIN to get back into normal phone mode.
- No longer can your child send your boss an email by accident.
Gadgets app
- Run apps when accessories connect
- Find accessory by seeing on a map where you last disconnected the accessory
Near Field Communication (NFC) can be used for more things than just payments like in iOS
The Glance Screen is like a low powered notification screen.
Wireless charging in some models
Standard USB charging cable (micro or newer type c)
Full desktop class browser which can switch from mobile user agent to desktop one
Social integration with contacts so when you get a new friend in Facebook or twitter they can show up as a contact
Glance screen
- Low powered screen that shows the time, date, next appointment and notification count.
Expand storage with SD cards
Battery Saver
Wi-Fi can automatically turn back on
- Turns off checking for email and other background tasks to help save battery
- Can automatically turn on at 20% battery
Configure apps from within the app instead of needing to leave and go to settings
When turning off WiFi, option to turn back on based on a time frame or when at a favorite place such as home
Cortana – Personal Digital Assistant with voice recognition
- Quiet Hours
  - Inner circle can break through
- Collection of news and other information that is important to you
- Reminders
  - Place
    - Cortana is your personal digital assistant. Here she is giving me a run down of my interests.
      
      Remind me to buy print cartridges next time I’m at the Best Buy off Rea road
    - Remind me to pick up groceries when I leave work
    - Remind me to start laundry when I arrive home
  - Person
    - Remind me to ask my Mom how her cat is doing next time I’m in contact with her (phone, email, text)
  - Time
- Text message with nicknames
  - Text message my wife on my way
  - Text message my manager I’m running late

2015 Climbing Goals Recap

Steve Lineberry — Wed, 30 Dec 2015 16:20:40 +0000

Onsight of Tricks for You (5.12a)

Erica does a year in review for her climbing goals (click here for her’s) so I decided to document mine as well. Below were some of my goals for 2015 and other thoughts on how the year went.

I really liked Erica’s 12 5.12’s in 2012 goal a few years ago (see post on cragmama here) so I decided to try to send 15 5.12’s in 2015. It doesn’t have the same ring to it but I ended up surpassing the goal with sending (excluding repeats) 20 5.12’s in 2015.

Left El Shinto (5.12b)

Ten Sleep helped a lot with this goal because I sent 6 5.12’s there with all of them being 2 goes except for one which I onsighted (Tricks for You 5.12a). By September I had achieved my goal with my 15th send of the year when I sent Fine Motor Control (5.12a).

After having some luck in the 5.12b range this year I was hoping to send a 5.12c at some point. I worked on Hard Rock Café (5.12c) several times but walked away with only a one hang. I had picked out what seemed like a perfect 5.12c for me in Ten Sleep called Left El Shinto. Unfortunately, others also felt like it was too perfect and in the recently released latest guidebook, the route had been downgraded to 5.12b. I did send the route but ended up giving myself a 5.12b credit for it.

Techman (5.12c)

After I sent Freaky Stylee (5.12a) earlier this year I decided to get on Techman (5.12c) with Erica this fall. Techman is a V5/6 boulder problem into some hard 5.11 climbing and shares the same 5.12a crux finish with Freaky Stylee. It ended up taking me 3 attempts to send and the send was epic. I almost fell off at crimpy crux and at two of the hard 5.11 moves later. What I was really excited about was the Freaky Stylee crux which I fell at so many times in the spring and in the past few years I did without any issues both times I tried it that day.

I use 8a.nu to track my sends and I really enjoy their ranking system. I set out a goal for my all time score to be equal to my yearly score. What this basically means is that the top 10 sends of my life happened this year. I wasn’t sure it was going to happen because I needed to have 10 of at least the following: 5.12b, 5.12a second go, 5.11d flash, 5.11b/c onsight. While at Ten Sleep I was able to accomplish this goal. Here’s a link so see how I did for the year.

Gangsta (5.12a)

I have bouldered well at the gym by getting a lot of V5’s and V6’s (including a stray V7 and V8). I was hoping to have an outside send of at least a V5 this year but it didn’t happen. We didn’t boulder outside at all this past year. My birthday bouldering bash was rained out in January, Hound Ears was postponed and since we were so ropes focused because of our Ten Sleep trip, we just didn’t make it a priority. Hopefully next year.

Check Your Grip (5.12a)

Lastly, it felt great to get redemption on a few routes that gave me issues last year. Freaky Stylee (5.12a) took me a total of 9 attempts and Gangsta (5.12a) took me a total of 16 attempts to send. I was also excited to get several sends that are steeper such as Lost Souls (5.12a) and Check your Grip (5.12a). Other memorable moments were sending three 5.12’s in a single weekend (Freaky Stylee (5.12a) on a Saturday and then Fired For Sandbagging (5.12a) and Michelin Man Original Finish (5.12b) on Sunday) and onsighting Tony The Tiger (5.11c).

Unable to Manually Start Workflows

Steve Lineberry — Mon, 22 Sep 2014 19:51:14 +0000

Recently, after we finished migrating our large external farm from SharePoint 2010 to SharePoint 2013, I started hearing complaints that some user’s could not manually start workflows. They would either get a 403 Forbidden or get the “Sorry, you don’t have access to this page” message.

The stack trace on the back end produced the following:

Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(HttpContext context) at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex) at Microsoft.SharePoint.SPSecurableObject.CheckPermissions(SPBasePermissions permissionMask) at Microsoft.SharePoint.WorkflowServices.StoreSubscriptionService.EnumerateSubscriptionsByEventSource(Guid eventSourceId) at Microsoft.SharePoint.WorkflowServices.ApplicationPages.WorkflowPage.ConstructStartArray() at Microsoft.SharePoint.WorkflowServices.ApplicationPages.WorkflowPage.OnLoad(EventArgs e)

Figuring out the problem just took a little investigation. I recently used this as a Demo for a SharePoint session I did recently at my local SharePoint Saturday. From that session I have a video of the issue and how I determined the cause. Skip to about 2:15 for the start of the issue and investigation. Click here to see the video

So basically the new SharePoint 2013 Workflow Manager is checking for Contribute access at the Site (SPWeb) scope when determining if someone should see the list of workflows for a list (see first line of the method in the code below).

// Microsoft.SharePoint.WorkflowServices.StoreSubscriptionService
public override WorkflowSubscriptionCollection EnumerateSubscriptionsByEventSource(Guid eventSourceId)
{
	this.context.Web.CheckPermissions(SPBasePermissions.EditListItems);
	WorkflowStore workflowStore = new WorkflowStore(this.context.Web);
	eventSourceId = StoreSubscriptionService.ConvertToGuidToken(eventSourceId, this.context.Web);
	WorkflowFile[] files = workflowStore.QueryWithGuid("0x0100AA27A923036E459D9EF0D18BBD0B9587", StoragePublishState.Unchanged, "WSEventSourceGUID", eventSourceId);
	return this.ConvertToWorkflowSubscriptionCollection(files);
}

So in our scenario, our users had read access to the site but contribute access on the list. This should allow them to start the workflow and it did in SP 2010. I currently have a Design Change Request (DCR) open with MS regarding this issue so hopefully it will be fixed soon. Once I hear more, I will update this post. In the meantime there seems to be two workarounds.

Workaround 1: Earlier in the code I determined that if you DON’T setup and connect a SharePoint 2013 Workflow Manager to the farm, then this code will never run and thus it will work just like it did in SP 2010. Of course the issue with this workaround is you can’t have any SP 2013 workflows.

Workaround 2: Basically give everyone that needs to manually start workflows contribute access to the site, and then break inheritance to all lists and libraries where the user DOESN’T need contribute access and remove their contribute access.

We ended up implementing the second workaround above which sucks for my users. I am hoping this is fixed soon as I have also seen other people complaining about it (http://sharepoint.stackexchange.com/questions/115311/manually-start-sharepoint-2010-workflow-in-sharepoint-2013-farm/)

Speaking at SharePoint Saturday Charlotte 2014

Steve Lineberry — Thu, 18 Sep 2014 18:37:42 +0000

I am speaking at the Charlotte SharePoint Saturday 2014 event this Saturday. Below is my abstract and slide deck if you are interested. If you are a reader of my blog and are going to the event, please stop by and say hello.

Session Title: Unwrapping the Black Box: Advanced SharePoint Troubleshooting and Forensics

Session Topic: SharePoint can often feel like a black box, and with little to no knowledge of internal workings, troubleshooting can be daunting. In this session, I remind you that SharePoint is nothing more than ASP.NET Web Forms and apply some of the same troubleshooting techniques to get you out of the dark. I will also delve into some SharePoint specific tools and demonstrate actual errors and troubleshooting where the resolution requires reading Microsoft SharePoint code.

Tools/Techniques

Internet Explorer F12 Developer Tools
Fiddler2
Developer Dashboard
ULS Viewer
SharePoint Manager
Reflector/ILSpy
SQL Profiler

Click here for the presentation including embedded videos of demos and scenarios.

SharePoint 2013 conflicts with custom site definition

Steve Lineberry — Sun, 30 Mar 2014 15:30:49 +0000

I was updating one of our custom Site Definitions from SharePoint 2010 to SharePoint 2013 recently and everything was going good until I tried to create a site from the updated definition. I kept getting the error:

Microsoft.SharePoint.SPException: The template you have 
chosen is invalid or cannot be found.

Searching on the internet told me the most common cause of this error was a conflicting ID for the template. I was pretty sure this couldn’t be the case since we followed the instructions here: http://msdn.microsoft.com/en-us/library/office/ms454677(v=office.14).aspx which stated:

Change the ID attribute of the Template element to a 
value of 10000 or more. This ensures that your ID will 
not conflict with future site definitions produced by 
Microsoft. If there are other custom site definitions 
on your target farm, make sure that each one has a 
unique ID.

and we had given our template an ID of 10000. I had previously updated another custom site definition of ours with an ID of 10001 without any issues.

So I decided to give a quick search in the SharePointRoot\template\1033\XML folder for anything that contains ID=”10000″. Sure enough I found two site definitions, mine and a new one that comes with SharePoint 2013 called the Academic Library.

I found this article: http://social.technet.microsoft.com/wiki/contents/articles/20149.sharepoint-2013-default-site-templates.aspx which discusses the new site definitions that come with SharePoint 2013. You can see it listed there as:

ID	Name	Title
10000	DOCMARKETPLACESITE#0	Academic Library
The Academic Library template provides a rich view and consumption experience for published content and management. Authors populate metadata and apply rules at the time of publishing, such as description, licensing, and optional rights management.(IRM). Visitors of the site can search or browse published titles and add authorized selections to their collection to consume, subject to the rights and rules applied by the author. The site provides an IRM-capable document library, a publishing mechanism for authors to publish documents, detailed views for each document, a check-out mechanism, and related search capabilities.

So it would seem that if you followed the recommendations for SharePoint 2010 and used an ID of 10000 for your custom site definition, then when you try to go to SharePoint 2013, your site definition won’t work.

This is an issue because there is not a way to change the template ID of a site after it’s been created through the API. Fortunately, I have found 2 ways to get around this. One of them I haven’t fully run to ground and verified that it works but the concept seems valid and the other isn’t supported by Microsoft.

Option 1:

This option I got the idea from this blog: http://iknowsharepoint2007.blogspot.com/2010/02/changing-sharepoint-site-definition.html. The basic idea is you export your site without using compression, change some xml configuration files so they use your new ID, and then import it back into your SharePoint environment. You might not even have to change any xml files since that post was for SP 2007. If someone tries this method, please comment below, otherwise if I find time to give it a try, i’ll update with my findings here.

Option 2:

This involved editing data directly in the SharePoint content database. This is unsupported by Microsoft but worked for me during my testing. Go to the AllWebs table in the content database for the site in question. You should be able to find your site listed by scanning the FullUrl column. Once found, write a SQL update statement which updates the WebTemplate column to the new site definition ID. This was an instant fix for me as I was able to immediately start the upgrade to SharePoint 2013 for that site collection.

It sucks that Microsoft told us they would never use Site Definitions ID of 10000 or more and then they go back on their word with SharePoint 2013. Anyways, I hope this helps someone else out trying to complete their migration to SharePoint 2013. If anyone finds a better way to fix the issue, please post in the comments below. Thanks.

Warning: SetCookie changes implementation in SharePoint 2013

Steve Lineberry — Sat, 29 Mar 2014 00:09:06 +0000

I was recently working on verifying some of my custom code worked in SharePoint 2013. I had some older code where I needed to set cookies and use them to remember user preferences. I was debugging my code and I noticed that all of my cookies were coming back either true or false instead of the value I put into them. I had been using a SharePoint JavaScript method called SetCookie. Below is the implementation that has existed in SharePoint for the previous 3 versions (2003, 2007, and 2010).

function SetCookie(name, value, path)
{
	document.cookie=name+"="+value+";path="+path;
}

But for some reason Microsoft decided to change the implementation of this method in SharePoint 2013 to the following:

function SetCookie(sName, value) {
    SetCookieEx(sName, value, false, window);
}
function SetCookieEx(sName, value, isGlobal, wnd) {
    var c = sName + (value ? "=true" : "=false");
    var p = isGlobal ? ";path=/" : "";

    wnd.document.cookie = c + p;
}

Notice this new method tries to evaluate the value into a boolean and then forcefully sets the cookie to true or false. So if you were storing anything other than boolean values in your cookies and used this method in previous versions of SharePoint, you will now need to update your code. For this you have two options:

Option 1: I found there is another method in SharePoint 2013 which still implements the SetCookie the same was as previous versions of SharePoint.

function SetMtgCookie(cookieName, value, path) {
    document.cookie = cookieName + "=" + value + ";path=" + path;

}

So you can easily do a search and replace for SetCookie to be replaced with SetMtgCookie and you’ll be good to go.

Option 2: This is the option I opted for. I decided that as tempting as doing a quick search and replace like I suggested in option 1 sounded, I wanted to remove my dependency on SharePoint’s implementation in case it changes again in the future. Since the older SetCookie is only one line, I just replaced my method call to that line:

document.cookie=name+"="+value+";path="+path;

It was a pretty simple change, only slightly more time taken than option 1 and I removed a dependency.

Anyway, I hope this helps someone else out when troubleshooting code migration to SharePoint 2013.

Steve Lineberry

Mixing Mobile Friendly Forms based auth with NTLM Windows auth in SharePoint

This is a special login page just for mobile devices. If you feel you reached this page in error, @Html.ActionLink("click here to restore normal login functionality", "Exclude", "Home").

You are currently logged in as: @Model.UserName @Html.ActionLink("Click here to logout", "Logout", "Home", new { ReturnUrl = Request.QueryString["ReturnUrl"] }, new { } ).

@if (string.IsNullOrEmpty(Request.QueryString["ReturnUrl"])) { Return to site }else{ Return to site }

If you have previously saved your password in your browser, select the username field above and then select autofill password at the top of the onscreen keyboard.