This project is read-only.

Client tooling


When we configured both windows and claims authentication we could not sign in to SharePoint from a client application like Word or Excel.
When we opend Word and want to save the document to SharePoint we get the login page of the claim provider. When we login to the claim provider we get a access denied message of SharePoint. Using the browser it all worked well.

After some investegation we found that the class autosignin inherits from Page. We have changed the inheritance to 'IdentityModelSignInPageBase'. This solved our problem with client tooling

file attachments


whorn76 wrote Jun 12, 2014 at 5:23 PM

I tried changing the inheritance to 'IdentityModelSignInPageBase' and it still gives us the access denied page when using Word or Excel.

Any other ideas?

wrote Jun 12, 2014 at 6:03 PM

arjancornelissen wrote Jun 13, 2014 at 7:23 AM

You also need to change the "autosignin.aspx" page with the following

<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %>
<%@ Register Tagprefix="SharepointIdentity" Namespace="Microsoft.SharePoint.IdentityModel" Assembly="Microsoft.SharePoint.IdentityModel, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="autosignin.aspx.cs" Inherits="OrbitOne.SharePoint.Claims.SignIn.Login.autosignin" MasterPageFile="~/_layouts/15/errorv15.master" %>

<asp:Content ID="Content1" ContentPlaceHolderId="PlaceHolderPageTitle" runat="server">
<asp:Content ID="Content2" ContentPlaceHolderId="PlaceHolderPageTitleInTitleArea" runat="server">
<asp:Content ID="Content3" ContentPlaceHolderId="PlaceHolderMain" runat="server">

whorn76 wrote Jun 16, 2014 at 4:20 PM

Still no luck. It looks like you may have made other modifications to the original source code? There is no autosignin.aspx.cs in the solution that I obtained. And also the original Inherits mentions "OribitOne.SharePoint.Claims.SignIn.AutoSignin", but your example adds a Login in the middle as well.

Granted I'm no C# expert or anything. Just know enough to be dangerous ;). Could you perhaps provide your source code for the solution?


wrote Jun 16, 2014 at 6:23 PM

arjancornelissen wrote Jun 16, 2014 at 6:23 PM

I also did some rebranding for my customer, so moved some file arround. I have attached our version

dlsumners wrote Sep 12, 2017 at 4:56 PM

Do you by chance have this solution packaged into a WSP for deployment into SharePoint?