Tag Info

New answers tagged

0

for a reason the authentication provider for my web application was changed from NTLM to kerberos. so i modify the Authntication provider to NTLM and now evertthing is working well.


0

SharePoint 2007 and 2010 used Classic authentication as default, while SharePoint 2013 use Claims as default. So the error is simple telling you that the databases are configured for Classic but mounted to a Claims web application. You can create a web application that uses Classic authentication with PowerShell, but i think that is like asking for ...


0

Coming back late to this but if you are still up an running is it because your services are load balanced across your two servers? The errors should tell you which machine is generating the logon attempt. It could be one of the following: Time is off - Kerberos by default requires all servers be within 5 minutes of each other, if the Auth token time ...


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() { ...


1

From the technical point of view you can use this one account for this purpose. From a best practice I would not recommend it. Enabling delegation is always a securitry threat. Please check out this Microsoft KB article for all the needed details: http://support2.microsoft.com/kb/2723073 From reading your questions I get the impression you are missing ...


0

if you are SharePoint online, i would suggest that you leverage the AppModel. Register an App Id and App Secret. Have your service build a context to SharePoint. You can use the SharePoint Web Toolkit to build a context to SharePoint in .NET. Using the Client Side Object Model (CSOM), request the current user information from SharePoint Online. You ...


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


1

ADFS: The TokenLifetime property can be set at the ADFS end using the command upon creation . Below is example is for 2 sec . Set this value to a high number ,so that the session never expires while working on page . Add-ADFSRelyingPartyTrust -Name "abc" -Identifier "https://abc/_trust/" -WsFedEndpoint "https://abc/_trust/" -TokenLifetime 2 ...


0

You can read this post. It should point you to the right direction: http://msdn.microsoft.com/en-us/library/hh446526.aspx



Top 50 recent answers are included