Tag Info

New answers tagged

0

Authentication is Web App level Configuration. But In your scenario, I would recommend this. Extend your web application to different zone and configure the FBA on that zone. Now set the new Host name to the site collection for that extended zone. ...


2

Are you pulling information into the page from anywhere else? Any elements on the page that may pull information from say another library will also need to have permissions set so that the user can access them. You can check ULS logs for more details on the path and user that is denied as well. Make sure it's not referring to your anonymous user - which ...


0

At the end I used this code to impersonate current user to local web service: try { Guid siteid = SPContext.Current.Site.ID; Guid webid = SPContext.Current.Web.ID; using (SPSecurityContext.GetWindowsIdentity().Impersonate()) { Label1.Text = WindowsIdentity.GetCurrent().Name; SOAPService ws = new SOAPService() { ...


0

I have exactly the same problem since 2-3 weeks! Changed our SharePoint and Project Server 2013 installation from NTLM based Authentication to NTLM+Form based authentication and now the Project Server active directory synchronization changes all Logon Accounts from the Project Server users from i:0#.w|domain\username to i:0.w|fbamembershipprovider\username! ...


1

The difference is in "authentication mode" settings. Windows authentication provides real windows user and then this would allow us to make resource requests from ASP.NET while impersonating the Windows identity of whoever was logged on. With forms authentication ASP.NET itself makes requests for system resources using the Application Pool account. Look ...



Top 50 recent answers are included