If you're getting this error, but you can login with forms, then your SecurityTokenService configuration is ok, but there's an issue with your web application settings (web.config/machine.config).
One possibility is that the SecurityTokenService app pool and Web Application app pool run under different different user's, and only the SecurityTokenService ...
I havent tried this for claims in SP2010, but in SP2007 this was done for FBA by adding PeoplePickerWildCard element to membership provider in web.config
<add key="AspNetSqlMembershipProvider" value="%" />
<add key="fbaMembers" value="%" />
You can follow steps below:
1) Create a copy of SignOut.aspx in the Layouts folder. Rename it as
2) Open the custom page in notepad\designer. In the function _spBodyOnLoad() replace windows.close() with windows.location("YourHomePageRelativeUrl");
3) Make this page the default sign out page for the web application using below command ...
I had the same problem when creating my custom login page, and the answer was to add the "/_layouts" to the front of the path I was linking to.
Creating a Simple Shared Login Screen
If you want some form of shared login screen, without needing the IP address or a feature or anything else, here's what I did to get that:
For each site involved, created a ...
The site will feature regular logon (forms)
For this I would recommend to use the Forms base or windows authentication
The site will contain some lists where the content is either retrieved
from local database or backoffice system
OOTB SharePoint Lists can be use to save and retrieve the data (local i.e. saved in SharePoint ContentDB) while Business ...
You need to authenticate the connection to SharePoint using the FBA user's credentials.
ClientContext clientContext = new ClientContext("http://YourUrlHere");
clientContext.AuthenticationMode = ClientAuthenticationMode.FormsAuthentication;
new FormsAuthenticationLoginInfo("username", "password");
You may extend the SharePoint Web application with FBA, to create an extranet-facing access point to provide access to the partners. Extending an existing SharePoint Web application provides a separate IIS Web site and you can group external users into a different security domain than internal users.
This approach makes it easier to manage different ...
If you can add users to the FBA Pack, but you can't login, that means that your SharePoint web application web.config/machine.config membership settings are good, but your SecurityTokenService web.config settings are not. Check your SecurityTokenService web.config membership settings and compare them to your web application web.config/machine.config ...
Try this solution:
Check if EnableADAL key is present
If not present then create new REG_DWORD key with name EnableADAL and value 0
This worked for me
This is typical of a SharePoint implementation.
If you think of SharePoint more as a platform than just an application, customization is expected and desired.
Whether you proceed with SharePoint as your platform or choose another platform most likely will depend on the resources you can secure to implement this. As SharePoint customization help is in ...
Please find a similar issue reported in msdn with FBA authentication and Opera browser.
As the post suggests,
Opera browser is not on the supported browser list for SharePoint. Chrome isn't on the list either, although that one normally works. Opera has always had issues with SharePoint and it isn't fixed in 2010. Here's the list of approved browsers.
If you extend a WebApplication you have to have some difference in the url (could be http vs https) otherwise SharePoint has no way of knowing which zone you're in.
But if you're using SharePoint 2010 then you don't need to extend to get the behaviour you want.
If you enable both Windows and FBA in your zone the default Login Page provides a LogonSelector ...
SharePoint 2010: How to Buy
You can use SharePoint 2010 to set up intranet, extranet, and Internet
sites. Intranet sites are licensed using a Server/CAL (Client Access
License) model. SharePoint Server 2010 is required for each running
instance of the software, and CALs are required for each person or
device accessing a SharePoint Server. ...
You need to put the page in its own library, set the anonymous access for the site to 'Lists and Libraries'. Then you need to allow anonymous access for the single library.
If you don't want to turn anonymous access on at all, then you'll have to create your login page as an application page (and this is how you should be creating a login page imho). The ...
You are overcomplicating things.
There is no need to change the applicationID. You can use the exact same FBA database that you were using for SharePoint 2010. The applicationID used is based on the ApplicationName in your membership provider settings in your web.config.
As long as you use the exact same membership provider settings, including the name of ...
Tools For use:
1. FBA Configuration Manager for SharePoint 2013 – Author and Credit goes to Steve Peschka. The download comes with a ReadMe file. Please read it, since you need to register the WSP that comes with it.
SharePoint 2013 FBA Pack – Author and Credit goes to Chris Coulson. Here is the documentation that will tell you how to install/activate/work ...
I found a source that may help you immensely. The following link walks you through how to use a PowerShell script to import a list of users from Excel and create them for FBA.
Importing and Exporting Data in Extranet Collaboration Manager (ExCM) 2010
You can also download the PowerShell source code from this link.
It looks like the code creating ...
And, here's an update: KB3203432 - https://support.microsoft.com/en-us/help/3203432/descriptionofthesecurityupdateforsharepointserver2016june13-2017 did seem to fix this problem (the 401 vs 403 issue) without using the module above. However, it then created another problem for us in our on-premises SP 2016 system with Office 2016 (and claims auth via AD ...
The functionality that IE is attempting is actually Office trying to authenticate the user on it's own against SharePoint. Chrome/FireFox doesn't have this level of integration and therefore just opens the document.
You can get around this by disabling Client Integration in central admin (Application Management > Authentication Providers I think, been a ...
Have a look at SharePoint 2010 FBA Pack:
A forms based authentication pack for SharePoint 2010. It includes web parts for registering users, changing passwords and password recovery. It includes tools for managing users and roles and for approving registrations.
Sounds like maybe you didn't configure the People Picker Wildcards in the web.config file? (I'll delete my answer if this turns out to not be the case as FBA is VERY finicky about how its configured and it could be a million different things!)
search cookieHandler in web.config of your webapplication, then add the persistentSessionLifetime property:
<cookieHandler mode="Custom" path="/" persistentSessionLifetime="1.0:0:0">
it seams the property just have ...
I found a timed job that has been resyncing the display name: Farm User Profile Service Proxy - User Profile to SharePoint Full Synchronization. Having disabled this (temporarily until I find out exactly what it does), I've not seen my 'fixed' display names reverting back to their former values.
Thanks sween_sp for the nudge in the right direction.
In the end, I didn't use the ASP:Login control. I just designed my own login box with two textboxes. Username and password.
My login box, and my change password box are in two panels on the page. One hidden the other not. The person logs in, checks with the database if it is valid and if they need to change their password, if so, hides the login box panel, ...