New answers tagged

0

Add following entry in web.config of your site. <appSettings> <add key="aspnet:MaxHttpCollectionKeys" value="5001" /> </appSettings> This should resolve your issue.


0

Sorry, I don't think it's possible in claims authentication because until and unless it is intercepted by ADFS it won't be authorized and hence SAML token won't be issued to particular user after issuing SAML token identity field under HttpContext is populated, Please read the below link Claims-based Authentication, ADFS 3.0, and SharePoint 2013 – ...


0

Setting up the object cache required 3 steps: add the super user and super reader account in Policy for web app. configure the both account for web application. In this make sure if you are passing the account in claims format. like this $wa = Get-SPWebApplication -Identity "" $wa.Properties["portalsuperuseraccount"] = "i:0#.w|DOMAIN\SuperUA" ...


0

Ok I got the problem. Did you configure the Cache SuperUser and SuperReader Accounts? It happens if they weren't configured. Please follow steps in this MSDN article to configure those accounts for your SharePoint 2013 Environment. Configure object cache user accounts in SharePoint Server 2013


0

Before doing the Custom login page for windows authentication, you have to configure your web application web.config file to authenticate current user credential against active directory. Here is a link which may help you on that. And Creating a Forms Based Authentication will be easy. You can get help from here on that. ADFS is not mandatory to these. But ...


1

In order to achieve what you need, you "simply" have to switch to Form-Based Authentication (FBA) at the Web application level, and make it point to a custom page you have to develop first. That custom page shows the form you like, and checks the credentials the way you like. A simple Google query will give you all links you need to build and setup a ...



Top 50 recent answers are included