9

"Keyset does not exist" means you need to give your web application pool identity account access to your certificate. Do this in the Certificates Snap In.


7

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 ...


6

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 ...


5

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 ...


5

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 ...


5

Try this solution: HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity 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


4

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 ...


4

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 ...


4

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 ...


4

Nico, 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 ...


4

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 ...


4

What you describe is standard for the way SharePoint list work. When you create a custom list you'll be able to add the columns (aka Fields) as your requirement needs. As you add fields they will appear on the list DispForm.aspx, NewForm.aspx, and EditForm.aspx forms. By default, the Display form will not have an "Add" button. This is only on the list view ...


3

I called Microsoft on this (case 11303​0110256288) and it's a product bug in 2013 - apparently a regression from 2010. Another customer had reported the same issue. It's an acknowledged bug with no KB yet. They hope to pick it up in an upcoming cumulative update but it wasn't know when to expect it yet.


3

Disabling and Enabling the Anonymous access at the Web Application resolved issue for me


3

I had faced the similar issue when i was working with STS. The reason you get the error is because there is no trust being established between the Sharepoint and STS . If i am not wrong you might be getting the error at the below lines of code :) This is definitely a certificate issue. SecurityTokenService sts = new ...


3

You can override the login page on the web application settings in Central Administration. You would need to create a login page to replace it with. There are a number of examples on the web, here is one you could start with: http://sivarajan.me/post/SharePoint-2013-Enabling-Custom-Login-Page-and-Mixed-Contents-Part-2 EDIT To answer your revised question,...


3

In SQL FBA DB we have one column as Locked(I do not remember the name exactly). It is of boolean type and you need to set it false. Then the user will be unlocked.


3

For FBA, you need to make sure the site is using SSL.


3

To expand on my comment, check out these links How to: Expose a SharePoint Application to the Extranet and Use Forms-Based Authentication AAMs *Explained : Redux (and Presentation) The first article is a brief rundown of how to do precisely what you want to do: extend an SP web application into 2 IIS web applications, each with different authentication ...


3

You can perform following steps to make the registration form available to anonymous users (i.e. prospected FBA users). Extend the web application and enable anonymous access to the extended site. Configure the FBA authentication from IIS. The steps to follow for enabling FBA are provided here Create registration form web part the will accept data from ...


3

You most only have a single profile for any one individual. SharePoint sees the identity as two different users, and they cannot be 'merged' together. If you are unable to switch to a single provider for all Web Applications/users, you may want to look at one UPA Service Application per Web Application. To give you an example, you may have a user come ...


3

"Anonymous" means two things: From a technical point of view (or "identification/who are you?"), you must set "Anonymous" access in IIS. This is for IIS to allow any un-authenticated request to come in, and display the FBA logon page, without IIS interfering for authentication. This means IIS does not handle anymore the authentication through Windows-...


3

The difference is here: All Windows Claims contain a 'w': i:0#.w And all Forms Claims contain an 'f': i:0#.f This would be the best way, in a generic sense, to determine if the user is a Domain or Forms-based user. This TechNet Wiki article goes into detail about what the various letters and symbols mean.


3

I was having the exact same problem. Using SharePoint 2016, Office 2016, and ADFS 4.0/2016, the only way I can get it to work is to disable ADAL. ADAL is not supported for on-premise Exchange, so I wonder if the same is true for SharePoint as well. SharePoint 2013 in the exact same environment works OK. Poking around in Fiddler, I can see a few ...


3

You can reuse the SharePoint 2013 FBA database in SharePoint 2016 or you can create /setup FBA in SharePoint 2016 from scratch. I would prefer to setup the FBA 1st then migrates the Site collections. Setup FBA in SharePoint 2016 using existing DB or brand new. if using the 2013 FBA database, backup the DB and restore in 2016 environment, complete the ...


2

Like Thomas said, you can take another road, but that one will require configuration as well (you need to make SharePoint trust that external Identity Provider and bind it to the Security Token Service which is not as easy as it sounds. For your requirement, you could create, by code, a custom MemberShip Provider and rely on hardcoded users. Waldek has a ...


2

If you don't want to use Windows based authentication, some plumbing is always involved I'm afraid. When using FBA, you indeed will have to manage your user database yourself. This cannot be done from within SharePoint by default, but I'm sure options exist to do this. Another option is to go for claims based authentication. In that case you'll have to ...


2

So, this turned out to be a database permission issue. Apparently the special database roles that come along with the generated ASP.NET membership framework-generated databases are required for all users who wish to do things with the membership database. Farm account has dbo, so that's not a problem and that's why the thing works in Central Administration....


2

I would tell you to look into SAML based authentication and configuring SharePoint to trust your Java application as a trusted provider, but that may not be as easy as it sounds, so here is a quick fix. Implement an application page (under layouts folder) and inherit from UnsecuredLayoutsPageBase Setup your Java app to send users to this page with the token ...


2

With SharePoint 2013 the same code will work with bit modification. As SP2013 supports code written in SP2010 as well, and it has both 14 hive and 15 hive, you need show in your code which mapped folders to look for. In your aspx file you need to write the full path of the mapped folders as shown below /_layouts/15/images/ or /_layouts/15/ Rest of all ...


Only top voted, non community-wiki answers of a minimum length are eligible