New answers tagged forms-authentication
0
What you are looking for is possible but will require quite some work and deep knowledge about kerberos.
Reverse proxy solutions like Microsoft TMG are doing what you would like to do. It is possible to implement "some kind" of reverse proxy that will take the username and password from an ASPX page, store the data in "some" place and use the reverse proxy ...
0
I had the same problem but it is resolved by assigning the
aspnet_Membership_FullAccess
aspnet_Roles_FullAccess
to the db user which used in the Role Provider and Membership Provider,
this Link will help you your problem, Use the IIS Manger Wizard to avoid mistakes in config files.
1
The issue is down to the good old double problem. When you are accessing the site via a browser using ntlm, SharePoint cannot impersonate the user accessing the site via browser and you access Sql Server as anonymous.
The solution is to impersonate as the web app account as you have done with RunwithElevatedPermissions or use Kerberos.
Kerberos has the ...
0
Using SPSecurity.RunWithElevatedPermission() solved my problem. The form now seems to work as intended.
0
This is the standard behaviour of the ActiveDirectoryMembershipProvider. I do not believe that this can be changed. Wherever you require the current user to be shown on your masterpage etc you can simply reference the SPUser.Name property after authenticating.
2
It was working fine until I changed the default zone's authentication method to allow FBA in addition to Win Auth (claims).
Instead of changing the default zone, I think you should have extended the web application. If you can't switch things back to how they where, I would consider to restore the web application:
Considerations when restoring a Web ...
1
You will need to use a webpart to redirect users to different pages,
Here's a freeware webpart available for SharePoint 2010 but I am pretty sure it will work with SP 2013 too.
SharePoint 2010 User Redirect
If you want to do it yourself then follow this article,
Redirection options in SharePoint and then follow steps under "Redirect from Deep URL"
...
0
Unfortunately, I don't think you can have your desired setup and you have to fully enable FBA authentication on zone1.
If your issue is merely avoiding confusion about authentication (not presenting a choice of 2 authentication providers), then I would suggest using the OrbitOne SharePoint Auto SignIn solution at http://spautomaticsignin.codeplex.com.
I ...
1
you need to make sure that you have setup your database correctly:
make sure that you put your SQL database connection string in the web.config!
In the web.config, you’ll see sections for the connection string and the providers. The and sections
lastly
Membership.CreateUser
reading up on the above, it indicates that it stores the values in App_Data ...
0
All user accounts, regardless of site type, are stored at the Site Collection level. You'll need to use different Site Collection (using the New-SPSite -SiteSubscription switch).
0
To mirror the TechNet thread, see http://sharepoint.nauplius.net/2013/04/sharepoint-foundation-2013-the-ldapmembershipprovider-and-ldaproleprovider-class/. The LdapMembershipProvider and LdapRoleProvider classes exist in Foundation 2013, but their methods have no logic in them and you'll have to develop your own provider.
Top 50 recent answers are included
