I greatly appreciate that you take the time to respond to people like me.
I did have everything set up and working using SQL, but the guys who are responsible for security told me I could not use SQL and had to use AD LDS (aka ADAM). I tried, a little, to change their minds, but didn't want to waste a lot of time arguing over
So... I looked a the link you provided, and one major difference about my situation is that I did not extend the web app. I'm using both Windows authentication and FBA in the default zone.
I've spent a lot of time looking at various instructions regarding the setup of AD LDS and SharePoint 2010 FBA. It seems they all vary a bit. But, I was finally able to access my FBA user (the only one I've created in AD LDS so far), from a people picker
in Central Admin. So, I am thinking and hoping that since the web.config for Central Admin seems to be setup properly that the one for the web app is also.
Could it be that FBA User Management is expecting fields in the user's record which are not defined in my AD LDS setup? Or, perhaps the fields are there, but empty, and that's a problem?
Also, I am not using a Role Provider for FBA since I don't need roles/groups for my situation; therefore, I have not added anything to the web.config files for Roles. (Anything that was there already, when SharePoint created the original web.config files,
is still there.)
Could this be a problem? - even though I am not enabling Roles in "Manage Forms Based Authentication Configuration".
(I keep finding new information which is possibly relevant to this issue, so I'm editing this post from time-to-time.)
If I try to add my one user (from AD LDS) to a SharePoint group for permissions for my site collection, this FBA user is not found by the people picker. So, perhaps there is still something not quite right with the web.config for the associated web app.