Great post

2 May 2011 7:10 PM

Looks great STeve, but if I want to authenticate in via AD (this is a off premise server), how can I chose to authenticate that way?

Charles Brown

4 May 2011 4:20 PM

Would it not be easier to create a custom login form and handle both authentication methods in one?

Steve

4 May 2011 6:58 PM

@Charles, it depends on your requirements, which is why I tried to stress that this was a simple example for one scenario. In this particular case I wanted all users to go through FBA so there was no need to handle both auth types.

Alexander

4 Aug 2011 2:27 PM

Hello, Steve. Thanks for great article!

Can i do that without change original default.aspx - just configure app to use custom login page?

Eric Raff

9 Sep 2011 4:31 PM

Found an interesting blog about using the custom login page field and specifying the trust provider. Thisi s the custom login page, not code option. Only issue is that logout breaks so.....

shojeeb.com/.../custom-sign-in-page-url-for-sharepoint-quick-way

wehr

16 Sep 2011 7:16 PM

first reading the article i wondered why not use a custom login page...

I seems to me that using the custom login page is not a good idea because the search application cannot handle the 302 Redirect. (highest level error - object moved)

now i do it the same way: replace the default.aspx in the IDENTITYMODEL\LOGIN folder.

and search crawler does fine.

btw. the search crawler solves the "IIS Sharepoint warm up" problem. crawling all site-cols in the web-app warms them up. rightly?!

Kevin

11 Nov 2011 8:04 PM

Hi Steve,

I implemented the code and it works. However, it's actually throwing an exception when I attached the code to the process and debugging it. Another thing I notice is the Sign in as different user link doesn't work, The query string got appended twice.

Thanks,

Kevin

David

4 Oct 2013 10:06 AM

Hi,

I have a problem. I get parse error 'could not load type MultiAuthLogin' even though I have registered the library in GAC.

<%@ Page Language="C#" CodeFile="~/Default.aspx.cs" Inherits="MultiAuthLoginPage.MultiAuthLoginPage.Default" MasterPageFile="~/_layouts/simple.master" %>

Please advise.

Thanks,

David.

Joel Hasler (joel.hasler@ioz.ch)

22 Apr 2014 1:12 PM

Hello Steve

Thank you very much for your blog post. It was very helpful for us. We implemented your solution, because the customer authenticate only over ADFS, but for SharePoint internally we need Windows Authentication (ex. Search). It works perfect for about 18000 Users :-)

The Customer has SharePoint 2013 Enterprise (CU October 13). The problem that we have is that it does not work for mobile clients (ex. iPhone or Windows Phones). We get there the Selection of multiple Providers.

We see in the URL that the requests are forwarded to /_layouts/15/mobile/authn_dispatch.aspx. Do you have an idea how we can get it also to work for mobile clients?

Thank you very much for your help in advance.

Best Regards
Joël

Heather Zigli

29 Apr 2014 4:02 AM

One thing I had to do - grant the ANONYMOUS LOGON account read and execute permission on the .dll file in the GAC. Users were experiencing 403 forbidden errors otherwise. Is this expected?

Joel Hasler

15 May 2014 2:44 PM

We found the solution with the help of Microsoft. We just choose the wrong Namespace :-) Here is the code from Microsoft:

using System;
using System.Collections.Specialized;
using System.Web;

public partial class MobileSignInPage : Microsoft.SharePoint.IdentityModel.Pages.MobileMultiLogonPage
{
protected override void OnLoad(EventArgs e)
{
try
{
//if this isn't a postback, then the user hasn't selected which
//auth provider they want to use
//in this case we want to always refer the person to forms login

if (!this.IsPostBack)
{
//grab all the query string parameters
System.Text.StringBuilder qp = new System.Text.StringBuilder(2048);
foreach (string key in this.Request.QueryString.Keys)
{
qp.Append(key + "=" + this.Request.QueryString[key] + "&");
}
//redirect to the forms login page
this.Response.Redirect("/_trust/default.aspx?" + qp.ToString());
}
}
catch (Exception ex)
{
//Debug.WriteLine(ex.Message);

}
}
}

Maybe it is helpful for someone :-)

hassan sayed issa20014

4 Aug 2014 2:25 AM

thanks

hassan sayed issa20014

4 Aug 2014 2:29 AM

thanks

SDF

19 Sep 2014 4:29 AM

alexandrad9x

5 Dec 2014 10:21 AM